Search results

I'll mark this thread [SOLVED] once this patch hits pve-no-subscription if you're good with that.

Edit: I re-read your post; after I upgrade, I'll let you know if I'm getting this syslog message as well. I have not upgraded yet, but the user above (Dunuin) said he upgraded from the test repo, didn't get VM freezing, but still go that syslog message:

Excellent, thanks Proxmox team! What is the cause of the "VM ### qmp command failed - VM ### qmp command 'query-proxmox-support' failed - unable to connect to VM ### qmp socket - timeout after 31 retries" syslog event that Dunuin reported above? Is this message safe to ignore?

It turns out rolling back pve-manager wasn't sufficient, I was still having issues after I tried rebooting a few VMs. I rolled back libproxmox-backup-qemu and pve-qemu-kvm as well: apt install pve-qemu-kvm=5.1.0-8 libproxmox-backup-qemu0=1.0.2-1. Stoiko, I didn't see your reply until after I...

It looks like you've got full nodes freezing. I'm seeing individual VMs freeze. Note that the fix from the thread linked above seems to have fixed it for me (downgrading pve-manager to 6.3-3): apt install pve-manager=6.3-3 reboot

After I posted this, I ran memcheck overnight (no errors) and booted back into Proxmox. At that point, all the VMs ran fine for ~36 hours. I just now had to restart a few VMs because I took storage offline for maintenance. When I attempted to boot the VMs again, the issue returned. I'm using...

EDIT 2: An updated version of pve-qemu-kvm is now available in the pve-no-subscription repository and should resolve this issue (version 5.2.0-4): https://forum.proxmox.com/threads/all-vms-locking-up-after-latest-pve-update.85397/post-379077...