qmp command 'system_reset' failed - unable to connect to VM 151 qmp socket - timeout after 31 retries

[sonuyos]

Hello,

I have over 10 servers running Proxmox and recently i upgraded proxmox from 6.2.x to 6.3.4, and since the upgrade i get this error randomly whenever i try to reset.

qmp command 'system_reset' failed - unable to connect to VM 151 qmp socket - timeout after 31 retries

It never used to come in 6.2.x

and at the same time, I get a lot of the following error too

Guest Agent is not running

Even tho i am using the same template as before, i install the VM and it works fine and then randomly throws that error, even tho the VM is still running and i can VNC into it. Then i have to restart the server and more often than not i get the qmp socket error.

NOTE: It is Windows 2012 R2 VM.

 

[Stefan_R]

Could you post your 'pveversion -v' output? Also check the logs for anything suspicious around the time when the error starts to occur ('journalctl -e'), and maybe post them too.

 

[sonuyos]

Could you post your 'pveversion -v' output? Also check the logs for anything suspicious around the time when the error starts to occur ('journalctl -e'), and maybe post them too.

pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.44-2-pve)
pve-manager: 6.3-3 (running version: 6.3-3/eee5f901)
pve-kernel-5.4: 6.3-3
pve-kernel-helper: 6.3-3
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.44-2-pve: 5.4.44-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.0-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve3
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.7
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-3
libpve-guest-common-perl: 3.1-4
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-6
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.8-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-5
pve-cluster: 6.2-1
pve-container: 3.3-3
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-1
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-8
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-5
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1

This is the output, and no suspicious activity, as i have seen many people are facing this issue.

 

[Stefan_R]

pve-qemu-kvm: 5.1.0-8

The issue most people are referring to only occurs on 5.2.0, and has a (potential) fix in 5.2.0-4. This would be something else then. (unless you downgraded before running the pveversion?)

You specifically mention the "Reset" command in the first post, does it always/only occur when you do that? If you can easily reproduce it, please share your VM config as well, and potentially try to capture a gdb trace after a hang as described here: https://forum.proxmox.com/threads/a...er-latest-pve-update.85397/page-2#post-377434

 

[sonuyos]

The issue most people are referring to only occurs on 5.2.0, and has a (potential) fix in 5.2.0-4. This would be something else then. (unless you downgraded before running the pveversion?)

You specifically mention the "Reset" command in the first post, does it always/only occur when you do that? If you can easily reproduce it, please share your VM config as well, and potentially try to capture a gdb trace after a hang as described here: https://forum.proxmox.com/threads/a...er-latest-pve-update.85397/page-2#post-377434

I might have made a mistake, the server whihc was facing the issue, i have upgraded to 5.2.0-4 however i am not sure if the issue still persist and i think i have given the output of a neighbouring server instead.

As for the Reset, i do not run the command, but do it from the Panel itself.

The moment i see this error again, i will take the gdb trace for it.