Guest VM Bluescreen VirtIO Disk

tim_die

New Member
Aug 3, 2021
2
0
1
25
Hello all,

a running Win10 VM has been changed from IDE to VirtIO by adding an VirtIO-Harddisk, installing the VirtIO driver and detaching the hard disks again. Now I encounter a bluescreen (BSOD) when I start the VM again, it restarts and then it works. So only the second attempt to start the VM fails with a bluescreen. Besides of that, the VM works when it started.

VM config:

Linux pve 5.4.128-1-pve #1 SMP PVE 5.4.128-1 (Wed, 21 Jul 2021 18:32:02 +0200) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@pve:~# qm config 129
balloon: 2048
boot: order=scsi0;ide2
cores: 2
cpu: host,flags=-hv-tlbflush
description: Neue Win10 TIA16 VM mit dem aktuellsten 20H2 Windows Update. Stand 06.07.2021%0A%0ABitte nur zum Klonen verwenden!
ide2: none,media=cdrom
memory: 8192
name: WIN10TIA16
net0: e1000=92:78:14:CC:88:4D,bridge=vmbr0
numa: 1
ostype: win10
scsi0: local-lvm:vm-129-disk-0,size=42G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=6d6bf62f-b56c-4894-aa4f-1604c21cd57c
sockets: 2
usb0: host=3-1.8
vcpus: 4

Pveversion
pve-manager/6.4-13/9f411e79 (running kernel: 5.4.128-1-pve)


What could be the problem there?
 
Last edited:
Seems like I resolved the problem by myself. In the Windows eventviewer one log was described:

Kernel Power ID 41: The system has rebooted without cleanly shutting down first.[..]
For me it seemed like during a normal shutdown of the VM guest, the host forces the VM to shutdown - leading to a BSOD just the first time after powering it on again. After installing the qemu agent, the BSOD disappeared. https://pve.proxmox.com/wiki/Qemu-guest-agent

Problem seems to be solved then.