Windows 11 stuck when I set CPU type yo host

[mnapps]

Hello everyone!

I am having an issue with my windows 11 vm on proxmox. I am trying to set the CPU type to host but windows 11 stuck and get into automatic repair screen.
If I set the CPU type to qemu64, windows boot normally. I would like to run hyper-v but I can't do that if I don't set the cpu type to host.
The strange thing is that I setup windows having the CPU type to host but after a reboot, it stuck into the automatic repair screen and the only way to boot windows again is to set the CPU type to qemu64 (or KVM64). Before I reboot and get it stucked I installed nvidia drivers for my GPU (which I pass through to the VM) and I also enabled hyper-v.

Here is my configuration :

pveversion
pve-manager/7.4-3/9002ab8a (running kernel: 5.15.107-1-pve)

/sys/module/kvm_intel/parameters/nested
Y

/etc/default/grud

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on initcall_blacklist=sysfb_init iommu=pt pcie_acs_override=downstream,multifunction nofb nomodeset"
GRUB_CMDLINE_LINUX=""

/etc/pve/qemu-server/100.conf

agent: 1
args: -cpu host,+kvm_pv_unhalt,+kvm_pv_eoi,hv_vendor_id=NV43FIX,kvm=off'
bios: ovmf
boot: order=scsi0;net0;ide2
cores: 8
cpu: host,hidden=1,flags=+pcid
efidisk0: local-lvm:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
hostpci0: 0000:01:00,pcie=1
ide2: Backup:iso/virtio-win-0.1.229.iso,media=cdrom,size=522284K
machine: pc-q35-7.2
memory: 16384
meta: creation-qemu=7.2.0,ctime=1680719952
name: Sunshine.204
net0: virtio=5E:B1:..:..:..:..,bridge=vmbr0,firewall=1
numa: 1
onboot: 1
ostype: win11
scsi0: local-lvm:vm-100-disk-1,iothread=1,size=256G,ssd=1
scsi1: local-lvm:vm-100-disk-3,iothread=1,size=1T
scsihw: virtio-scsi-single
smbios1: uuid=000000000000,manufacturer=000000=,product=QQ>
sockets: 1
tpmstate0: local-lvm:vm-100-disk-2,size=4M,version=v2.0
usb0: host=1-7.2
usb1: host=0bda:8176
vmgenid: 08a7c376-d940-4226-a8ac-...

Physical hardware

• CPU : Intel Core i5-13400F
• GPU: GeForce RTX3060

Any suggestion?

Thank you!

 

[Moayad]

Hi,

Can you post the output of the pveversion -v as well? I would try to disable the hyper-v on the Windows 11 to narrow down the issue if it's from the GPU pass through or from the hyper-v.

 

[mehdital]

Hi,

Can you post the output of the pveversion -v as well? I would try to disable the hyper-v on the Windows 11 to narrow down the issue if it's from the GPU pass through or from the hyper-v.

I have a 13400 and the exact same problem. Disabled Hypervisor, but doesn't help. I migrated my Proxmox host to the i5 13400 from an i5 10500. Just plugging the OS ssd to the new system. Upgraded to kernel 6.2 and Proxmox 8 for better support of newer intel cpus to no avail.

pveversion -v

proxmox-ve: 8.0.2 (running kernel: 6.2.16-6-pve)
pve-manager: 8.0.4 (running version: 8.0.4/d258a813cfa6b390)
pve-kernel-6.2: 8.0.5
proxmox-kernel-helper: 8.0.3
pve-kernel-5.15: 7.4-4
proxmox-kernel-6.2.16-6-pve: 6.2.16-7
proxmox-kernel-6.2: 6.2.16-7
pve-kernel-6.2.16-4-bpo11-pve: 6.2.16-4~bpo11+1
pve-kernel-5.15.108-1-pve: 5.15.108-2
pve-kernel-5.15.107-1-pve: 5.15.107-1
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-3
libknet1: 1.25-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.4
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.7
libpve-guest-common-perl: 5.0.4
libpve-http-server-perl: 5.0.4
libpve-rs-perl: 0.8.5
libpve-storage-perl: 8.0.2
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 3.0.2-1
proxmox-backup-file-restore: 3.0.2-1
proxmox-kernel-helper: 8.0.3
proxmox-mail-forward: 0.2.0
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.2
proxmox-widget-toolkit: 4.0.6
pve-cluster: 8.0.3
pve-container: 5.0.4
pve-docs: 8.0.4
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.3
pve-firmware: 3.7-1
pve-ha-manager: 4.0.2
pve-i18n: 3.0.5
pve-qemu-kvm: 8.0.2-4
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.12-pve1

vm config:

agent: 1
balloon: 0
bios: ovmf
boot: order=virtio0;net0;ide2
cores: 16
cpu: host
efidisk0: local-zfs:vm-104-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
hookscript: local:snippets/cpu-pin.sh
hostpci0: 0000:01:00,pcie=1,x-vga=1
hostpci1: 0000:02:00.0,pcie=1
ide2: local:iso/virtio-win-0.1.225.iso,media=cdrom,size=519590K
machine: pc-q35-8.0
memory: 24576
meta: creation-qemu=6.2.0,ctime=1670252283
name: windows11
net0: e1000=76:D7:CA:24:DF:87,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win11
scsihw: virtio-scsi-single
smbios1: uuid=76df4de2-6920-40cc-a620-1f63e6844302
sockets: 1
tpmstate0: local-zfs:vm-104-disk-1,size=4M,version=v2.0
usb0: host=1209:4f54,usb3=1
usb1: host=046a:b102,usb3=1
usb2: host=05ac:024f,usb3=1
usb3: host=0bda:8771,usb3=1
vga: none
virtio0: local-zfs:vm-104-disk-2,size=1T
vmgenid: 4c307a89-cc94-4290-a88e-2b73b747d06d

 

[Moayad]

Hello,

Did you try to disable the Secure boot on the VM? (make a backup for the VM before that) and I would try `cpu: host,hidden=1` in the VM config.

 

[mehdital]

Hello,

Did you try to disable the Secure boot on the VM? (make a backup for the VM before that) and I would try `cpu: host,hidden=1` in the VM config.

hidden=1 has done the job for me! thank you so much!
Finally I see benchmark results within 95% of native performance on a VM!

 

[mehdital]

Hello,

Did you try to disable the Secure boot on the VM? (make a backup for the VM before that) and I would try `cpu: host,hidden=1` in the VM config.

Actually, I tried setting back to just host without hidden=1 and now the VM also works!