Help error query-proxmox-support

[Carlosmf]

Goodnight
I ask for help please with this error, it is constant that the steps I have to take to solve it can help it is very urgent

Thank you so much

VM 100 qmp command failed - VM 100 qmp command 'query-proxmox-support' failed - unable to connect to VM 100 qmp socket - timeout after 31 retries


Virtual Environment 7.1-8

 

[dylanw]

Hi,

Do you know what was running on the host/vm which led to the issue? Have you tried rebooting the VM? Can you post the output of pveversion -v and cat /etc/pve/qemu-server/100.conf?

 

[Jorge A. Ponce]

Dear, good night...

I have the same fault. I enclose the data that they asked the other gentleman.

root@Promox:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-8 (running version: 7.1-8/5b267f33)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-2
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3






root@Promox:~# cat /etc/pve/qemu-server/108.conf
bootdisk: sata0
cores: 4
ide2: none,media=cdrom
memory: 2048
name: WinVM
net0: e1000=72:E5:01:6FC:2F,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win7
sata0: Raid1:108/vm-108-disk-0.qcow2,size=32G
scsihw: virtio-scsi-pci
smbios1: uuid=e66d8869-c347-4026-84bd-8429d626107a
sockets: 1
vmgenid: b64aee31-f090-42ab-9509-335644a8066e


I thank you in advance for your help.

 

[dylanw]

Hi Jorge,

What runs in the VM? Were there any tasks carried out on the VM (e.g., a backup) which triggered the error message?
Did the VM go into a hung state or did it recover?

 

[Jorge A. Ponce]

Hello!! thanks for answering


I'll tell you a little. The server currently runs 10 vm, 9 linux and one with windows 7. They were recovered from a backup of another server that no longer works
A clean installation of Debian was done and then Proxmox (The previous server was installed like this too and never gave this error.)
Everything works fine but after hours or days... the virtual machine is inaccessible and only by turning off and on the vm, access to it is recovered.

the error shown in the log is always the same.

"Jan 20 21:54:09 Promox pvedaemon[1645]: VM 111 qmp command failed - VM 111 qmp command 'query-proxmox-support' failed - unable to connect to VM 111 qmp socket - timeout after 31 retries"

 

[dylanw]

This seems like a pve-kernel-5.13.19-2 issue that we have seen with Window's VMs that have SATA disks attached. It has been fixed [1] in 5.13.19-3, so please do a full upgrade and reboot of your host system, to see if it resolves the issue.

[1] https://git.proxmox.com/?p=pve-kernel.git;a=commit;h=25aba572caffbcf8173abf0e292a7a27b13563c9

 

[Krusty]

I had the same problem, but with the HD in IDE format.
I removed the VM from Proxmox to continue validating.