Why this becomes a problem
A Hyper-V checkpoint can leave the active state in AVHDX differencing disks rather than the parent VHDX. Converting only the parent loses changes. Generation 2 machines also expect UEFI and often Secure Boot behavior that differs from an old BIOS-style QEMU template.
How VMBook approaches it
VMBook separates the native Hyper-V machine from an explicit conversion workflow. It can manage the Hyper-V source in place, then create a QEMU-owned copy when migration is intentional. That reduces pressure to convert merely to obtain a common inventory.
Recommended workflow
- Shut down the guest and merge every checkpoint.
- Record Generation 1/2, Secure Boot and disk-controller settings.
- Convert to a new qcow2 file and configure matching BIOS or UEFI.
- Boot offline first; validate storage drivers, networking and activation.
Limits and checks
Encrypted or shielded workloads need additional recovery planning. A successful qemu-img conversion does not prove that Windows, applications or licensing will accept the new virtual hardware.
Primary documentation
Frequently asked questions
What problem does this guide solve?
Merge Hyper-V checkpoints before conversion and preserve the original VHDX. A converted disk needs a QEMU machine that matches the original firmware generation and can present boot and network hardware Windows understands.
How does VMBook help?
VMBook separates the native Hyper-V machine from an explicit conversion workflow. It can manage the Hyper-V source in place, then create a QEMU-owned copy when migration is intentional. That reduces pressure to convert merely to obtain a common inventory.
What should I verify before using it?
Encrypted or shielded workloads need additional recovery planning. A successful qemu-img conversion does not prove that Windows, applications or licensing will accept the new virtual hardware.

