VM is suspending randomly

[neuron]

A Windows VM (1 of 3) on a PVE host randomly suspended twice within a few hours. The first time, I tried to start it again but it wouldn't work, so I had to do a Stop then restart and it came back online just fine. Then backups ran, ended successfully, and about an hour later, the same VM ended up suspended again. I tried to start it but it failed on its own. A stop/start worked. Two other VMs on the same host are not experiencing this issue.

I'm not seeing anything specific in the logs that are causing this but I noticed one thing:

Aug 05 00:40:24 pve4 pvescheduler[1262364]: INFO: Starting Backup of VM 122 (qemu)
Aug 05 00:40:44 pve4 pvestatd[4619]: VM 122 qmp command failed - VM 122 qmp command 'query-proxmox-support' failed - got timeout
Aug 05 00:40:44 pve4 pvestatd[4619]: status update time (6.362 seconds)

I also notice that a system cron job is running on/around this time. SSDs are all healthy (SMART status OK) and there is plenty of RAM and storage space. Are there additional logs I can look at to figure out the cause? Any specific reasons why Proxmox would suspend a VM - or perhaps why a VM would suspend?

Edit: clarification

 

[oguz]

hi,

I'm not seeing anything specific in the logs that are causing this but I noticed one thing:

Aug 05 00:40:24 pve4 pvescheduler[1262364]: INFO: Starting Backup of VM 122 (qemu)
Aug 05 00:40:44 pve4 pvestatd[4619]: VM 122 qmp command failed - VM 122 qmp command 'query-proxmox-support' failed - got timeout
Aug 05 00:40:44 pve4 pvestatd[4619]: status update time (6.362 seconds)

this is likely not related to your issue.

which version are you on? please post the output from pveversion -v

Any specific reasons why Proxmox would suspend a VM - or perhaps why a VM would suspend?

did you check the power settings inside windows?

 

[neuron]

I'm still having this issue. Seems to happen weekly so far around 11pm, then again at 2am. Will try to check Windows itself. Definitely a strange one. Here's my PVE version:

proxmox-ve: 7.2-1 (running kernel: 5.15.39-1-pve)
pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85)
pve-kernel-5.15: 7.2-6
pve-kernel-helper: 7.2-6
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-4.15: 5.4-17
pve-kernel-4.15.18-28-pve: 4.15.18-56
pve-kernel-4.15.18-10-pve: 4.15.18-32
ceph: 15.2.16-pve1
ceph-fuse: 15.2.16-pve1
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
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-7
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
openvswitch-switch: 2.15.0+ds1-2+deb11u1
proxmox-backup-client: 2.2.5-1
proxmox-backup-file-restore: 2.2.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.5-1
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-11
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

 

[oguz]

Seems to happen weekly so far around 11pm, then again at 2am

do you have any scheduled backups around those times?

could you also check the journals around the time where it suspends the VM?

 

[neuron]

Power settings were set to sleep after 2 hours so I’m hoping that was it. Changed it to high performance plan with no monitor or sleep enabled.

PVE backups start at 12am daily.

If this continues to happen, I will investigate further. Thanks for the aha moment with power options though. That would be the only thing that makes sense.