Nested Virtualization - Windows 10 stuck on Windows logo on boot

[Ryszard]

HI! I'm running Proxmox 7.2 on Intel i9-12900 and I can't get Nested Virtualization to work, whenever I try to install WSL2 on a guest VM, after required reboot I get stuck on black screen with Windows logo only (VM still works if I move it to a different node in my cluster with different CPU). I've tried to use kernel 5.17, different machine types (pc-i440fx / q35) but still with no luck. Does anybody know what could cause it / how to fix it? Thank you very much for help!

My VM config:

agent: 1
boot: order=scsi0;ide2;net0
cores: 4
cpu: host
ide2: none,media=cdrom
kvm: 1
machine: pc-i440fx-6.0
memory: 16384
name: test
net0: virtio=1A:67:8A:01:1E:19,bridge=vmbr0
numa: 0
ostype: win10
scsi0: zfs-data:vm-650-disk-0,discard=on,size=100G
scsihw: virtio-scsi-pci
smbios1: uuid=8e9700c0-ff8a-4ffa-8041-a90a10a6f691
sockets: 2
vmgenid: 199a67d4-48b9-45f7-a1e8-b926dfa709d6

lsmod | grep kvm:

kvm_intel             311296  11
kvm                   913408  1 kvm_intel
irqbypass              16384  1 kvm

cat /sys/module/kvm_intel/parameters/nested

Y

 

[Ryszard]

Same thing happens when I try to enable WSL on Windows 11, but if I try to run VirtualBox with Linux, it runs fine. Any ideas?

 

[Ryszard]

Any help?

 

[dcsapak]

mhmmm just tested here on an i7-12700k with pve 7.2 (and 5.15 kernel) and it worked. the only difference is i used windows server 2022 (with q35/ovmf) to test. i could enable wsl2 and install a distribution.
are there any logs inside the vm that might give a hint? bios/microcode update maybe?

 

[Ryszard]

On Windows Server 2022 it works, but on Win10 it doesn't so I guess it's a problem with Windows and not Proxmox.