[GH-ISSUE #506] bug: `create guest qemu ...` will fail #141

New issue

Open

opened 2026-02-28 00:40:43 +03:00 by kerem · 2 comments

kerem commented

2026-02-28 00:40:43 +03:00

Owner

Originally created by @NemoDacremont on GitHub (Oct 30, 2025).
Original GitHub issue: https://github.com/Telmate/proxmox-api-go/issues/506

Problem

When running the command create guest qemu with the new CLI, it will fail (proxmox v9.0.11, latest master commit) :

> proxmox-api-go -i create guest qemu --file qemu.json 123 pve
Error: 501 Method 'GET /nodes/pve/unknown/123/config' not implemented
Usage:
  proxmox-api-go create guest qemu GUESTID NODEID [flags]

Flags:
  -h, --help   help for qemu

Global Flags:
  -d, --debug             debug mode
  -f, --file string       file to get the config from
  -i, --insecure          TLS insecure mode
  -p, --proxyurl string   proxy url to connect to
  -t, --timeout int       api task timeout in seconds (default 300)

2025/10/30 19:22:21 501 Method 'GET /nodes/pve/unknown/123/config' not implemented

Where qemu.json is :

{
        "name": "test-qemu01",
        "bios": "seabios",
        "tablet": true,
        "memory": 128,
        "ostype": "l26",
        "cores": 1,
        "sockets": 1,
        "cpu": "host",
        "numa": false,
        "kvm": true,
        "hotplug": "network,disk,usb",
        "iso": "none",
        "boot": "order=ide2;net0",
        "scsihw": "virtio-scsi-pci",
        "network": {
                "0": {
                        "bridge": "vmbr0",
                        "firewall": true,
                        "id": 0,
                        "macaddr": "B6:8F:9D:7C:8F:BC",
                        "model": "virtio"
                }
        }
}

Originally created by @NemoDacremont on GitHub (Oct 30, 2025). Original GitHub issue: https://github.com/Telmate/proxmox-api-go/issues/506 ### Problem When running the command `create guest qemu` with the new CLI, it will fail (proxmox v9.0.11, latest master commit) : ```sh > proxmox-api-go -i create guest qemu --file qemu.json 123 pve Error: 501 Method 'GET /nodes/pve/unknown/123/config' not implemented Usage: proxmox-api-go create guest qemu GUESTID NODEID [flags] Flags: -h, --help help for qemu Global Flags: -d, --debug debug mode -f, --file string file to get the config from -i, --insecure TLS insecure mode -p, --proxyurl string proxy url to connect to -t, --timeout int api task timeout in seconds (default 300) 2025/10/30 19:22:21 501 Method 'GET /nodes/pve/unknown/123/config' not implemented ``` Where `qemu.json` is : ```json { "name": "test-qemu01", "bios": "seabios", "tablet": true, "memory": 128, "ostype": "l26", "cores": 1, "sockets": 1, "cpu": "host", "numa": false, "kvm": true, "hotplug": "network,disk,usb", "iso": "none", "boot": "order=ide2;net0", "scsihw": "virtio-scsi-pci", "network": { "0": { "bridge": "vmbr0", "firewall": true, "id": 0, "macaddr": "B6:8F:9D:7C:8F:BC", "model": "virtio" } } } ```

kerem commented

2026-02-28 00:40:44 +03:00

Author

Owner

@NemoDacremont commented on GitHub (Oct 30, 2025):

I've been seeing this issue at several places : integration tests (well the config I'm using here is the integration tests), but also when trying to migrate vmInfo from the legacy CLI. I think the use of "Guests" is kind of confusing, I guess it is a way to factorize the common code of LXC and Qemu vm, but maybe this should only be internal logic and not be exported ? I feel like the CLI becomes confusing as well.

I'm working on finding the root cause but I think I already found it

@NemoDacremont commented on GitHub (Oct 30, 2025): I've been seeing this issue at several places : integration tests (well the config I'm using here is the integration tests), but also when trying to migrate `vmInfo` from the legacy CLI. I think the use of "Guests" is kind of confusing, I guess it is a way to factorize the common code of LXC and Qemu vm, but maybe this should only be internal logic and not be exported ? I feel like the CLI becomes confusing as well. I'm working on finding the root cause but I think I already found it

kerem commented

2026-02-28 00:40:44 +03:00

Author

Owner

@NemoDacremont commented on GitHub (Oct 30, 2025):

Most of the issue was my using deprecated config, a better one would be

{
    "name": "test-qemu01",
    "bios": "seabios",
    "tablet": true,
    "memory": {
        "capacity": 2048
    },
    "ostype": "l26",
    "sockets": 1,
    "cpu": {
        "type": "host",
        "cores": 1
    },
    "numa": false,
    "kvm": true,
    "hotplug": "network,disk,usb",
    "boot": "order=ide2;net0",
    "scsihw": "virtio-scsi-pci",
    "network": {
        "0": {
            "bridge": "vmbr0",
            "firewall": true,
            "id": 0,
            "macaddr": "B6:8F:9D:7C:8F:BC",
            "model": "virtio"
        }
    }
}

But there was issues with the CLI as well, I'll make the PR tomorrow

@NemoDacremont commented on GitHub (Oct 30, 2025): Most of the issue was my using deprecated config, a better one would be ```json { "name": "test-qemu01", "bios": "seabios", "tablet": true, "memory": { "capacity": 2048 }, "ostype": "l26", "sockets": 1, "cpu": { "type": "host", "cores": 1 }, "numa": false, "kvm": true, "hotplug": "network,disk,usb", "boot": "order=ide2;net0", "scsihw": "virtio-scsi-pci", "network": { "0": { "bridge": "vmbr0", "firewall": true, "id": 0, "macaddr": "B6:8F:9D:7C:8F:BC", "model": "virtio" } } } ``` But there was issues with the CLI as well, I'll make the PR tomorrow