Windows VMs with CPU Type Host not booting

[Franini]

What I am trying to achieve:
I have a VM where I through a GPU and a USB card. My goal is to use this VM as my daily PC.
I also want nested VM to be enabled because I want to use WSL.

What I did:
I upgraded my PVE from 6.4 to 7.1 so I could set up a Windows 11 VM. I had no problems with it and everything worked as intended after the upgrade.
Nested VM is already enabled.

What the problem is:
When I set the CPU type to Host, it doesn't matter if I set it to an existing Windows VM or try to set one up. The VM starts up, so to speak.
It stops before it can load Windows. When I try to set up a VM, a bluescreen appears after a few seconds.

If I set the CPU type to host in a Linux VM, I don't have this problem. When I run the lscpu command, I get the correct CPU information.




Infos:
The Test VM is without GPU and USB card passtrought

bios: ovmf
boot: order=ide2
cores: 1
cpu: host
efidisk0: SSD-970-500G:vm-104-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
ide2: isos:iso/Win11_English_x64v1.iso,media=cdrom
machine: pc-q35-6.1
memory: 4096
meta: creation-qemu=6.1.1,ctime=1646165769
name: TestVM
numa: 0
ostype: win11
smbios1: uuid=4642b845-fab3-42d0-bc06-acc2c90e1da9
sockets: 1
tpmstate0: SSD-970-500G:vm-104-disk-1,size=4M,version=v2.0
virtio0: SSD-970-500G:vm-104-disk-2,size=32G
vmgenid: 5031e17c-f292-4bc1-b718-44adf8f07481

This results in "Stop code: SYSTEM THREAD EXCEPTION NOT HANDELD"

I already tryed to set different flags.


Systeminfos:


Result of pveversion -v

proxmox-ve: 7.1-1 (running kernel: 5.15.19-2-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-12
pve-kernel-5.15: 7.1-11
pve-kernel-5.13: 7.1-7
pve-kernel-5.4: 6.4-12
pve-kernel-5.15.19-2-pve: 5.15.19-2
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.4.162-1-pve: 5.4.162-2
pve-kernel-5.4.128-1-pve: 5.4.128-2
pve-kernel-5.4.124-1-pve: 5.4.124-2
pve-kernel-5.4.119-1-pve: 5.4.119-1
pve-kernel-5.4.114-1-pve: 5.4.114-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph-fuse: 14.2.21-1
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.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-3
libpve-guest-common-perl: 4.1-1
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libqb0: 1.0.5-1
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.3.0-2
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-6
pve-cluster: 7.1-3
pve-container: 4.1-4
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-5
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-2
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1

On the Consol of Proxmox occures the following Error when I try to start a Windows VM with CPU set to host:

 

[dcsapak]

maybe setting 'options kvm ignore_msrs=1' into a file in /etc/modprobe.d/ helps? (reboot after that)

also there were reportedly more problems with windows nested wsl with amd than with intel

 

[Franini]

You are great!
Works like a charm. I spent hours trying different configurations and it was just a small option
I am so happy right now. Have a great day
I would say the case is closed.

 

[rcwsr]

Sorry for bump but this also worked for me too, thanks!

Switching from qemu64 to host CPU, my win10 vm was bsod just after boot. But adding the above in a modprobe on pve host fixed it.

 

[iflywhirlybirds]

I hate to bring this back from the dead. Forgive my ignorance but I'm having a hard time understanding the solution, I created a file in /etc/modprobe.d, a .conf file, put the above line in it but it still won't boot. Any help would be appreciated. Thanks!

 

[dcsapak]

I hate to bring this back from the dead. Forgive my ignorance but I'm having a hard time understanding the solution, I created a file in /etc/modprobe.d, a .conf file, put the above line in it but it still won't boot. Any help would be appreciated. Thanks!

since that issue is already 2 years old, and i guess your kernel and hardware is quite different, it's probably not the exact same issue, could you please open a new thread for that?

 

[carl.debilly]

Thanks, I had a BSOD with a Win 11 VM using the cpu=host, proxmox 8.2.2 and the fix worked perfectly! Thanks @dcsapak!

 

[ollibraun]

For me it was PVE 8.2.4 with a CPU “12 x Intel(R) Xeon(R) E-2236 CPU @ 3.40GHz (1 Socket)” - a server migrated from ESXi would crash into a BSoD if I didn't use a virtual CPU type. After entering the line it worked with the processor type “host”.

Server 2019 Essentials, no Hyper-V service running

 

[sealbro]

I have a similar issue BSOD "SYSTEM THREAD EXCEPTION NOT HANDELD" with Windows 11

agent: 1
args: -cpu host,hv_vapic,hv_stimer,hv_time,hv_synic,hv_vpindex,+invtsc,-hypervisor
bios: ovmf
boot: order=ide0;net0
cores: 2
cpu: host
efidisk0: local-lvm:vm-1102-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
ide0: local-lvm:vm-1102-disk-1,size=64G
machine: pc-q35-9.0
memory: 4096
meta: creation-qemu=9.0.2,ctime=1725519663
name: win11-tm2
net0: e1000=<hidden>,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
scsihw: virtio-scsi-single
smbios1: uuid=<hidden>
sockets: 1
tpmstate0: local-lvm:vm-1102-disk-2,size=4M,version=v2.0
vmgenid: <hidden>

CPU(s) 8 x 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (1 Socket)

Kernel Version Linux 6.8.12-1-pve (2024-08-05T16:17Z)

Boot Mode EFI

Manager Version pve-manager/8.2.7/3e0176e6bb2ade3b

All works fine if removed -hypervisor