Why this becomes a problem
A VMDK may be monolithic, split into extents, sparse or part of a snapshot chain. Converting the wrong descriptor or only one extent can create an image that looks valid but lacks recent data. Even a correct qcow2 file may not boot if the new VM uses a different firmware or storage controller.
How VMBook approaches it
VMBook reads VMware descriptions and VMDK inputs, estimates image work and keeps the source while producing a new image. Its visible QEMU configuration makes the new firmware, disk bus and network model reviewable instead of burying migration choices behind an import button.
Recommended workflow
- Shut down and consolidate all VMware snapshots.
- Copy the VMX, descriptor and every VMDK extent.
- Run image information and consistency checks before conversion.
- Create qcow2 as a new file, boot it offline, then verify data and networking.
Limits and checks
Do not delete the VMware source after the first successful boot. Application activation, guest tools, network identity and workload-level consistency need separate verification.
Primary documentation
Frequently asked questions
What problem does this guide solve?
Power the VMware guest off, consolidate its snapshots, keep every VMDK extent together, and convert a copy. Disk conversion changes the container—not the guest firmware, drivers or virtual hardware expectations.
How does VMBook help?
VMBook reads VMware descriptions and VMDK inputs, estimates image work and keeps the source while producing a new image. Its visible QEMU configuration makes the new firmware, disk bus and network model reviewable instead of burying migration choices behind an import button.
What should I verify before using it?
Do not delete the VMware source after the first successful boot. Application activation, guest tools, network identity and workload-level consistency need separate verification.

