Windows VM randomly stops responding

[UntouchedWagons]

About 40 minutes ago my windows VM running Blue Iris completely stopped responding, I couldn't RDP in, qemu guest agent stopped responding and I couldn't access blue iris through its web interface. My only course of action was to reset the VM. I believe this started happening when I passed through an NVidia Quadro P400 for object detection.

I checked proxmox's syslog and didn't see anything of note and I checked the windows VM's event viewer (VM is running Server 2019) and it doesn't mention any issues.

agent: 1
args: -cpu host,kvm=off
balloon: 0
bios: ovmf
boot: order=virtio0
cores: 6
cpu: host
efidisk0: virtualization:vm-215-disk-1,efitype=4m,pre-enrolled-keys=1,size=1M
hostpci0: 0000:83:00,pcie=1
machine: pc-q35-6.0
memory: 6144
name: BlueIris
net0: virtio=E6:EB:89:BA:AF:A6,bridge=vmbr0
numa: 0
onboot: 1
ostype: win10
scsihw: virtio-scsi-single
smbios1: uuid=a981ea6b-0912-45e0-8a88-8a662df95d2a
sockets: 1
vga: virtio
virtio0: virtualization:vm-215-disk-0,cache=writeback,discard=on,iothread=1,size=60G
virtio1: vm-storage:vm-215-disk-0,backup=0,cache=writeback,discard=on,iothread=1,size=675G
vmgenid: 11e18745-2193-4a5b-9618-7cb4ba59fba8

This is the VM config.

 

[dcsapak]

whats the output of 'pveversion -v' ?

 

[UntouchedWagons]

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.11: 7.0-10
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-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.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

 

[UntouchedWagons]

Anyone have any ideas? The VM locked up again yesterday and I had to reset it.

 

[dcsapak]

could you try without the 'args' line and instead modify the cpu line to 'cpu: host,hidden=1' ?
this would enable some hyper-v integrations of kvm that may help...

also can you post the journal from a time where the vm hangs ? maybe someone else sees something...

 

[UntouchedWagons]

Okay I'll give that a try. Where would I find the journal?

[Edit] The NVidia driver won't start, code 43.

 

[dcsapak]

Okay I'll give that a try. Where would I find the journal?

by typing 'journalctl' e.g. the current boot can be selected with 'journalctl -b' and the one before that with 'journalctl -b -1'

[Edit] The NVidia driver won't start, code 43.

mhm thats weird...