Hi, I've recently upgraded from Proxmox 7 to Proxmox 8.2.4 and I'm running into an issue with running commands on a VM using QEMU Guest Agent using API calls.
This previously worked fine on Proxmox 7 but does not work anymore on Proxmox 8.2.4
What DOES work:
- API Calls to proxmox, e.g. get PVE Version: https://{{hostname}}:8006/api2/json/version (or rebooting VM etc.)
{
"data": {
"version": "8.2.4",
"release": "8.2",
"repoid": "faa83925c9641325"
}
}
What does NOT work:
- Executing a command on the VM using QEMU Guest agent: https://{{hostname}}:8006/api2/json/nodes/{{nodename}}/qemu/{{vmid}}/agent/exec
- I get the HTTP Status code "596" back, and time to complete request is rather high (> 5s). In Proxmox 7 I used to get back status code 200 OK when doing exactly the same call.
in the journalctl of the VM I can see that the command arrived but it does not get executed (here I try to initiate a reboot of the VM)
Jul 11 12:30:29 eylab0 qemu-ga[437]: info: guest-ping called
Jul 11 12:30:29 eylab0 qemu-ga[437]: info: guest-exec called: "sudo reboot -h now"
This used to work perfectly on Proxmox 7. For automation purposes I depend on running commands using the API on VMs, proved to be very efficient.
QEMU Guest Agent on VM is enabled. I initially noticed the failre on my debian 11 VMs, I then tried on a freshly installed debian 12 VM but noticed the identical behaviour.
Any ideas?
This previously worked fine on Proxmox 7 but does not work anymore on Proxmox 8.2.4
What DOES work:
- API Calls to proxmox, e.g. get PVE Version: https://{{hostname}}:8006/api2/json/version (or rebooting VM etc.)
{
"data": {
"version": "8.2.4",
"release": "8.2",
"repoid": "faa83925c9641325"
}
}
What does NOT work:
- Executing a command on the VM using QEMU Guest agent: https://{{hostname}}:8006/api2/json/nodes/{{nodename}}/qemu/{{vmid}}/agent/exec
- I get the HTTP Status code "596" back, and time to complete request is rather high (> 5s). In Proxmox 7 I used to get back status code 200 OK when doing exactly the same call.
in the journalctl of the VM I can see that the command arrived but it does not get executed (here I try to initiate a reboot of the VM)
Jul 11 12:30:29 eylab0 qemu-ga[437]: info: guest-ping called
Jul 11 12:30:29 eylab0 qemu-ga[437]: info: guest-exec called: "sudo reboot -h now"
This used to work perfectly on Proxmox 7. For automation purposes I depend on running commands using the API on VMs, proved to be very efficient.
QEMU Guest Agent on VM is enabled. I initially noticed the failre on my debian 11 VMs, I then tried on a freshly installed debian 12 VM but noticed the identical behaviour.
Any ideas?