[SOLVED] all qmp commands fail

May 22, 2024
3
1
3
Hello,

I'm trying to do a qm suspend on a VM and each and every VM I have fails with qmp timeouts. Example:

VM 201 qmp command 'stop' failed - got timeout

In journalctl -e I see the following timeouts:
May 21 18:52:56 vms qm[577016]: VM 201 qmp command failed - VM 201 qmp command 'stop' failed - got timeout
May 21 18:53:04 vms pvestatd[1557]: VM 201 qmp command failed - VM 201 qmp command 'query-proxmox-support' failed - got timeout

# pveversion -v | grep -E "proxmox-ve|kvm|backup-client"
proxmox-ve: 8.2.0 (running kernel: 6.8.4-3-pve)
proxmox-backup-client: 3.2.2-1
pve-qemu-kvm: 8.1.5-6

Even running the qm stop or qm suspend command from command-line directly fails.

I only have 3 guest VMs and it fails on all 3. Ubuntu, Debian and FreeBSD.

I've rebooted the guests, the host, and ensured both are fully up to date... doesn't matter. The commands fail.

Any help/insight here would be wonderful. Thank you!
 
Last edited:
I thought this was an issue with Proxmox Backup being in the picture, it's not. I can't do anything with snapshots, backups, copies. All "qmp" commands time out breaking any attempt at trying to backup VMs on this host.
 
vmxnet3 NIC driver was the culprit, apparently. Switched NICs to VIRTO and suddenly qmp commands all succeed and backup, suspend, snapshot - all operations function.

Why is this not mentioned in the documentation anywhere?
 
Last edited:
  • Like
Reactions: Kingneutron

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!