New Windows 11 VM Fails Boot After Update

I fixed it thanks to some other infos here from the forums.

Solution for me:

vm.conf
args: -cpu host,hv_passthrough,level=30,-waitpkg
(remove "cpu:" info line)

set /sys/module/kvm/parameters/ignore_msrs to Y

  • temporary
echo "Y" > /sys/module/kvm/parameters/ignore_msrs

  • persistent
echo "options kvm ignore_msrs=1" >> /etc/modprobe.d/kvm.conf
modprobe -r kvm
modprobe kvm


Sources:
https://forum.proxmox.com/threads/w...n-windows-guest-on-13th-gen-intel-cpu.131950/
https://pve.proxmox.com/wiki/Nested_Virtualization#Troubleshooting

Thanks everyone
 
i've just had this problem as well, based on previous posts I tried using "x86-64-v2-AES" as the CPU-type and this resolved it for my windows 11 workstation VM.

I'll try tofi's post above later to see if that also works for me. I'm not intending to use anything nested, but then again, I may need docker or WSL so....
 
Same here, Win11, after coming back to VM shutdown, tried to start, got boot loop into Win recovery.

Changing CPU type to "x86-64-v2-AES" immediately resulted in successful boot.

Not sure if this was a failed/incomplete Windows update that was automatically initiated, but here's some extra details for anyone looking to troubleshoot this further:
- Initial Win11 install was from ISO, build 22631. VM Config: CPU: Host, VirtIO, guest tools/QEMU guest agent: Enabled, Machine: pc-q35-9.0, Display: SPICE (qxl, memory=32)
- After changing CPU type and booting successfully, `winver` shows Windows Version: Win11 23H2 (build 22631.2861)
 
You must log in or register to reply here.
Top Bottom