[SOLVED] Windows 11 VM Crashes Host PC

[NojuHD]

Hello Guys,

i have a WIndows 11 VM with a Nvidia 980 ti passthrough, i can start and shotdown without problems. But when windows goes in Energy save mode and i try to resume after a couple of hours my whole Proxmox host "crashes" (i cant access web gui or ping him).

Does anyone have an idea what the Problem could be?

br
NojuHD

 

[oguz]

hi,

Does anyone have an idea what the Problem could be?

can you post the VM configuration here? qm config VMID

also which version of PVE are you using currently? pveversion -v

But when windows goes in Energy save mode and i try to resume after a couple of hours my whole Proxmox host "crashes" (i cant access web gui or ping him).

does disabling the energy save mode inside windows mitigate this problem?

 

[NojuHD]

does disabling the energy save mode inside windows mitigate this problem?

Yes the Problem only occurs when Windows goes in energy save mode.

can you post the VM configuration here?

Following my conf:

root@pve:~# qm config 9999
agent: 1
args: -cpu host,-hypervisor,+svm -smbios type=1,manufacturer="Gigabyte Technology Co. Ltd.",product="TRX40 AORUS XTREME"
balloon: 0
bios: ovmf
boot: order=scsi0;net0
cores: 12
cpu: host,hidden=1,flags=+ibpb;+pdpe1gb
description: hookscript%3A local%3Asnippets/simple-taskset-hookscript.sh
efidisk0: OS-SSD-1:vm-9999-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
hostpci0: 0000:21:00.0,pcie=1,x-vga=1,romfile=gtx980ti.rom
hostpci1: 0000:4d:00,pcie=1
hostpci2: 0000:50:00,pcie=1
hostpci3: 0000:55:00,pcie=1
ide0: WD-USB:iso/virtio-win-0.1.215.iso,media=cdrom,size=528322K
ide2: WD-USB:iso/Win11_German_x64v1.iso,media=cdrom,size=5448018K
kvm: 1
machine: q35
memory: 32768
meta: creation-qemu=6.1.1,ctime=1649610497
name: PC
net0: virtio=CE:9B:1E:BC:51:09,bridge=vmbr0,firewall=1
numa: 1
ostype: win11
scsi0: OS-SSD-1:vm-9999-disk-1,cache=unsafe,discard=on,size=128G,ssd=1
scsi1: /dev/disk/by-id/ata-CT500MX500SSD1_2135E5CA1F7C,backup=0,size=488386584K
scsihw: virtio-scsi-pci
smbios1: uuid=80e86f10-1153-4b6e-b204-173525338647
sockets: 1
tablet: 0
tpmstate0: OS-SSD-1:vm-9999-disk-2,size=4M,version=v2.0
vga: none
vmgenid: b5906a29-c5d2-46ac-b892-0a6854b01a7f
vmstatestorage: WD-USB

also which version of PVE are you using currently?

This are my current versions:

root@pve:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.30-2-pve)
pve-manager: 7.2-3 (running version: 7.2-3/c743d6c1)
pve-kernel-helper: 7.2-2
pve-kernel-5.15: 7.2-1
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.30-2-pve: 5.15.30-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-5-pve: 5.13.19-13
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-8
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-6
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.2-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.1.8-1
proxmox-backup-file-restore: 2.1.8-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-10
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-1
pve-ha-manager: 3.3-4
pve-i18n: 2.7-1
pve-qemu-kvm: 6.2.0-5
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-2
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]

only occurs when Windows goes in energy save mode.

i see that in your VM configuration you have a lot of disk and PCI passthrough going on.

my guess would be that the VM is sending suspend signal to the hardware which could cause a hang on the host...