Hi all,
I’m running into an issue with WSL2 inside a Windows Server 2025 VM after upgrading to Linux Kernel 7.0 and QEMU 11, and I’m hoping someone else has seen this or can point me in the right direction.
Environment
- Proxmox cluster with 2 nodes
- Node 1: ASRockRack X470D4U + Ryzen 7 3700X
- Node 2: ASRockRack X470D4U2T + Ryzen 9 5900X
- Shared VM migration between nodes is required
- Windows Server 2025 VM running WSL2 (Debian 13)
To allow live migration between these two CPUs, I’m using a custom CPU profile with only flags supported by both processors
Working Setup
- Kernel 7.0 + QEMU 10
VM boots fine with custom CPU Profile
WSL2 works and my Debian 13 installation executes (when starting the Debian 13 environment it does say wsl: Nested virtualization is not supported on this machine)
Live migration between nodes works
Issue (after upgrading to QEMU 11)
With the same custom CPU profile VM enters a boot loop and eventually lands in Windows Recovery
Behavior with different CPU types
- Host CPU type
Boots fine
WSL2 works
Cannot migrate (expected due to CPU mismatch) - Default CPU type (x86-64-v3)
Boots fine
Migration works
WSL2 does not work (WSL2 is unable to start as virtualization is not enabled for this machine) - New Custom CPU type with the new suggested flags added
Boots fine
WSL2 does not work (WSL2 is unable to start as virtualization is not enabled for this machine
In short
- QEMU 10 → everything works as expected
- QEMU 11 → WSL2 only works with host CPU profile, but that breaks migration
- Any attempt to combine migration-compatible CPU profile and nested virtualization leads to either bootloop (without the new suggested flags) or booting VM without WSL2 working (with level=30;-cet-ibt;-cet-ss flags)
Is there a recommended CPU profile that supports:
- migration between Zen 2 / Zen 3
- AND working virtualization for WSL2?
Thanks in advance!