Why this becomes a problem
A plain QEMU command can be difficult to assemble correctly: machine type, firmware, accelerator, graphics, storage controller, network card and installation media all interact. The worst failure mode is not an error—it is a guest silently falling back to slow software emulation or booting with hardware that its installer cannot drive.
How VMBook approaches it
VMBook detects the host and composes the command visibly. On an x86-64 Windows 11 PC, the normal path is an x86-64 guest with WHPX; a different guest architecture uses emulation. The application keeps the exact command available so a developer can reproduce or troubleshoot the result outside the GUI.
Recommended workflow
- Install Windows Hypervisor Platform from Windows Features.
- Install QEMU from a trusted current package.
- Create the VM with the correct guest architecture and BIOS or UEFI.
- Check the displayed command for -accel whpx and keep the original disk during testing.
Limits and checks
WHPX has documented limitations around some legacy VGA modes and unusual MMIO behavior. Same-architecture acceleration also does not turn an Arm guest into an accelerated guest on an x86 host.
Primary documentation
Frequently asked questions
What problem does this guide solve?
WHPX is QEMU’s Windows Hypervisor Platform accelerator. It gives QEMU hardware acceleration through the Hyper-V layer rather than asking QEMU to take exclusive control of the processor virtualization extensions.
How does VMBook help?
VMBook detects the host and composes the command visibly. On an x86-64 Windows 11 PC, the normal path is an x86-64 guest with WHPX; a different guest architecture uses emulation. The application keeps the exact command available so a developer can reproduce or troubleshoot the result outside the GUI.
What should I verify before using it?
WHPX has documented limitations around some legacy VGA modes and unusual MMIO behavior. Same-architecture acceleration also does not turn an Arm guest into an accelerated guest on an x86 host.

