[SOLVED] Windows 10 VM´s BSOD

[Petr.114]

Hello there.
Past 3 days we have hard times with Windows 10 virtual machines.
We are runnich cluster with 8 nodes, eveything is up to date and the problem occurs on every node.
BSOD is showing all the time, sometimes when booting, sometimes after few minutes of fresh started VM.

Spoiler: There is some info

proxmox-ve: 6.1-2 (running kernel: 5.3.18-2-pve)
pve-manager: 6.1-7 (running version: 6.1-7/13e58d5e)
pve-kernel-5.3: 6.1-5
pve-kernel-helper: 6.1-5
pve-kernel-5.0: 6.0-11
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.3.18-1-pve: 5.3.18-1
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.14-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-12
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-4
libpve-storage-perl: 6.1-4
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-19
pve-docs: 6.1-6
pve-edk2-firmware: 2.20191127-1
pve-firewall: 4.0-10 pve-firmware: 3.0-5
pve-ha-manager: 3.0-8
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-3
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-6
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

Spoiler: QM 1 config

#192.168.3.149
#
#server s VPN do OKD
agent: 0
args: -machine type=q35,kernel_irqchip=on
boot: c
bootdisk: sata0
cores: 4
machine: q35
memory: 4096
name: OKD
net0: e1000=32:47:31:da:65:b6,bridge=vmbr0
numa: 1
onboot: 1
ostype: win10
protection: 1
smbios1: uuid=4a94677f-b7fa-4ff1-b55c-131966443271
sockets: 1
virtio0: local-zfs:vm-115-disk-1,cache=writeback,size=50G

Spoiler: QM 2 config

bootdisk: ide0
cores: 2
ide0: local-zfs:vm-172-disk-0,cache=writeback,size=32G
memory: 4096
name: Win10ProTest
net0: e1000=76:2E:04:1B:83:6D,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
parent: updated_and_clean
scsihw: virtio-scsi-pci
smbios1: uuid=61f7db04-8cbd-4346-bba0-b9fb175dce23
sockets: 1
vmgenid: cfb010a8-7ae1-4822-a6a5-45f2fb2c7702

I will be glad for any idea what may be wrong.
If you want me to post more info, let me know.
Thank you.


EDIT: We fixed the problem by updating the kernel from 5.3 to 5.4. Windows VM´s are stable now.

 

[Alwin]

We are runnich cluster with 8 nodes, eveything is up to date and the problem occurs on every node.

Including the VirtIO drivers and updates for Windows?

BSOD is showing all the time, sometimes when booting, sometimes after few minutes of fresh started VM.

Which subsystem is failing? The BS have a ID, you can find more information for those on the Microsoft website.

 

[Petr.114]

Yes, Windows was updated (but some of the windows virtuals was not able to proceed the update because the virtual died when updating) and VirtIO drivers installed.
There was bunch of BSOD IDs, almost every time different one.

Spoiler: failures

IRQL not less or equal
UNEXPECTED STORE EXCEPTION
driver_irql_not_less_or_equal
PFN_LIST_CORRUPT
Page Fault In Nonpaged Area
KMode Exception Not Handled
system service exception
Critical Process Died

But as i said, after installing pve-kernel-5.4 and restarting nodes, everything works fine.
apt-get install pve-kernel-5.4