PVE 7.1-8: Windows-VMs crashes after a few days

[Patrick215]

Hello there,

I've just upgraded to a new root server and started with the latest Proxmox-Version. There I have the problem, that my Windows-VMs (Windows 10/11) crashes after a few days. The VM looks online and is visible in PVE, but it doesnt answer for ping requests anymore and I can't connect to the VM-Display via PVE. I have to stop the VM via PVE or SSH and to start it again to work properly. The same VM previously ran without any problems on another host with PVE 6.3.
The logs says, that the qmp command "query-proxmox-support" failed and theres no connection to the VM socket anymore. The timeout log entry is shown until i restart the VM.

My other Linux-VMs (Debian Buster, Ubuntu Server 20.04.....) are working 24/7 without any problems.

Has someone an Idea how to solve this problem?


Software-Versions:

pve-manager/7.1-8/5b267f33 (running kernel: 5.13.19-2-pve)

QEMU emulator version 6.1.0 (pve-qemu-kvm_6.1.0)
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers

VM-Config:

boot: order=sata0;ide2;net0
cores: 4
ide2: none,media=cdrom
machine: pc-i440fx-5.2
memory: 6144
name: ****-Win-01
net0: e1000=BE:E5:C7:9A:5E:BB,bridge=vmbr10
numa: 0
onboot: 1
ostype: win10
sata0: Datastore-****:182/vm-182-disk-0.qcow2,size=50G
scsihw: virtio-scsi-pci
smbios1: uuid=****
sockets: 1
vmgenid: ****

Syslog:

Dec 20 03:03:40 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - got timeout
Dec 20 03:03:41 hv01 pvestatd[1282]: status update time (6.570 seconds)
Dec 20 03:03:50 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:03:50 hv01 pvestatd[1282]: status update time (6.589 seconds)
Dec 20 03:04:00 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:04:01 hv01 pvestatd[1282]: status update time (6.580 seconds)
Dec 20 03:04:10 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:04:10 hv01 pvestatd[1282]: status update time (6.589 seconds)
Dec 20 03:04:21 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:04:21 hv01 pvestatd[1282]: status update time (6.595 seconds)
Dec 20 03:04:30 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:04:31 hv01 pvestatd[1282]: status update time (6.696 seconds)
Dec 20 03:04:40 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:04:40 hv01 pvestatd[1282]: status update time (6.595 seconds)
Dec 20 03:04:50 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:04:51 hv01 pvestatd[1282]: status update time (6.575 seconds)
Dec 20 03:05:00 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:05:01 hv01 pvestatd[1282]: status update time (6.609 seconds)
Dec 20 03:05:10 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:05:10 hv01 pvestatd[1282]: status update time (6.614 seconds)
Dec 20 03:05:20 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:05:21 hv01 pvestatd[1282]: status update time (6.591 seconds)
Dec 20 03:05:30 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:05:30 hv01 pvestatd[1282]: status update time (6.586 seconds)
Dec 20 03:05:40 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:05:41 hv01 pvestatd[1282]: status update time (6.683 seconds)
Dec 20 03:05:50 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:05:51 hv01 pvestatd[1282]: status update time (6.585 seconds)
Dec 20 03:06:00 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:06:00 hv01 pvestatd[1282]: status update time (6.584 seconds)
Dec 20 03:06:10 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:06:11 hv01 pvestatd[1282]: status update time (6.590 seconds)
Dec 20 03:06:20 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:06:20 hv01 pvestatd[1282]: status update time (6.596 seconds)
Dec 20 03:06:30 hv01 pvestatd[1282]: VM 182 qmp command failed - VM 182 qmp command 'query-proxmox-support' failed - unable to connect to VM 182 qmp socket - timeout after 31 retries
Dec 20 03:06:31 hv01 pvestatd[1282]: status update time (6.581 seconds)

 

[tom]

We have several reports, almost all are using SATA as disk bus.

=> Please change to IDE (no driver needed) or consider a change to VirtIO SCSI (recommended, extra drivers needed).

 

[Patrick215]

Thanks for your advice, I will try this and give a Feedback at the End of the month at latest.

 

[Ruflex]

Hi All. Same here Win VM has had a sata system drive for almost 10 years.
After migration to Proxmox7 VM hung every 30 minutes

 

[Laimonas Vijūnas]

Had same issue. Changed Disk form Sata to IDE and VM is stable. It's just strange, because I have multiple Windows VM in this server, with sata disks configuration, but it effected only one VM.

 

[Mr. A]

+1, both Windows VM just freeze (1 x 10 1 x 11) now on 7.1-8

Seems to have got worse when I did a routine update on PVE last week.

 

[Patrick215]

I have changed my affected Win10-VM to use VirtIO SCSI instead of SATA and I have no crashes anymore since 7 days. It seems to work.

Is this an officially known bug in the new PVE version?

 

[zash1958]

Same problem here, made me a sleepless night :-(
PMX latest updates and Server-2016 as a standard VM. SATA configured.

Fortunately I found the thread here with a solution.
Changing the driver to IDE solves the problem completely! IDE is slow, but the customer can work without any interrupts and we change the driver to VirtIO in the weekend.

But what the heck causes the problem? Is this kernel-related?