Still Hai Pham Thanh here — I’m replying from a different account because my company email couldn’t log in to respond. I think my previous message didn’t explain the actual problem clearly enough, so it might have caused some confusion. The bug you mentioned doesn’t seem related to what we’re seeing. In our case, the issue happens specifically when Nova’s cpu_models is set to IceLake variants (Icelake-Server-noTSX or Icelake-Server). With those models, Windows 11 VMs go into a boot loop after enabling nested virtualization features like Hyper-V or WSL. Windows 10 works fine, and Windows 11 also works fine if we use older CPU models like Broadwell or Cascadelake. The part about our compute nodes using Emerald Rapids CPUs was just to give full context — it’s not the cause. Update: I suspect this might be a QEMU-side issue, so I’ve also opened a report on the QEMU GitLab. If anyone wants to follow it: https://gitlab.com/qemu-project/qemu/-/issues/3215