Why this becomes a problem
The old model assumed a desktop hypervisor could own VT-x or AMD-V directly. Modern Windows may place Hyper-V underneath the whole operating system when WSL2, Virtual Machine Platform, Credential Guard or memory integrity is active. VirtualBox can detect that situation and use Hyper-V as its engine, but Oracle has documented significant performance degradation on some hosts. Users experience this as a green-turtle mode, slower guests or advice to turn Windows features off.
How VMBook approaches it
VMBook composes QEMU with the WHPX accelerator. WHPX is designed for third-party virtual machine monitors on top of Hyper-V, so the intended Windows 11 configuration is coexistence: keep WSL2 and Hyper-V, then let QEMU request acceleration through the platform API. VMBook also lists native Hyper-V machines and WSL distributions separately instead of pretending they are QEMU guests.
Recommended workflow
- Confirm virtualization is enabled in firmware and Windows Security.
- Enable Windows Hypervisor Platform; keep WSL2 or Hyper-V enabled if you use them.
- Install a current QEMU build, then let VMBook show whether WHPX was selected.
- Test one copied guest and compare boot, disk and graphics behavior before migration.
Limits and checks
WHPX does not make every legacy guest or graphics mode fast, and QEMU’s own documentation lists Windows-specific limitations. Keep VirtualBox when its guest additions or appliance workflow is essential; use a copied disk when comparing.
Primary documentation
Frequently asked questions
What problem does this guide solve?
Do not disable WSL2, Hyper-V or Windows security features merely to make a VM manager happy. QEMU can use WHPX, Microsoft’s supported Windows Hypervisor Platform interface, while those features remain enabled.
How does VMBook help?
VMBook composes QEMU with the WHPX accelerator. WHPX is designed for third-party virtual machine monitors on top of Hyper-V, so the intended Windows 11 configuration is coexistence: keep WSL2 and Hyper-V, then let QEMU request acceleration through the platform API. VMBook also lists native Hyper-V machines and WSL distributions separately instead of pretending they are QEMU guests.
What should I verify before using it?
WHPX does not make every legacy guest or graphics mode fast, and QEMU’s own documentation lists Windows-specific limitations. Keep VirtualBox when its guest additions or appliance workflow is essential; use a copied disk when comparing.

