Vmconverter: __top__

The source VM is powered off. The converter directly reads the source disk files (e.g., .vmdk ), interprets their block-level metadata, and writes a new disk image in the target format. Tools like qemu-img convert excel here. This method is simple, fast, and safe because the disk is quiesced. However, it requires downtime.

Organizations often switch virtualization vendors due to licensing changes (e.g., VMware’s shift to per-core licensing) or feature sets. A VMConverter allows a systematic escape from vendor lock-in. For example, converting a fleet of 500 ESXi VMs to KVM on Proxmox can save millions in annual licensing fees. The converter is the strategic lever for negotiation. vmconverter

Beyond disk formats, the virtual hardware signature differs. A VM built for ESXi expects the VMware SVGA II graphics adapter, the VMXNET3 network driver, and the LSI Logic SAS storage controller. Boot that same disk image on Hyper-V, which presents a Synthetic Network Adapter and a Hyper-V SCSI controller, and the guest OS will crash with a blue screen (INACCESSIBLE_BOOT_DEVICE). This is the core problem: a VM is bound to its hypervisor’s driver ecosystem. The VMConverter’s primary task is to transcend these incompatibilities by manipulating both the disk geometry and the OS configuration. Modern VMConverters (such as VMware vCenter Converter, StarWind V2V Converter, Microsoft Virtual Machine Converter, and open-source tools like qemu-img with virt-v2v ) operate through one of two fundamental paradigms: cold migration (offline conversion) or hot migration (live conversion). The source VM is powered off

The source VM remains running while conversion occurs. This is far more complex. The converter installs an agent (or uses a hypervisor’s native API) to take a point-in-time snapshot. It then reads the snapshot’s blocks, converts them, and writes to the target. Meanwhile, it tracks all new writes to the source disk (the “dirty block log”). Once the initial copy is complete, the converter pauses the source VM briefly, syncs the dirty blocks, transfers control, and boots the target VM. VMware vCenter Converter’s “hot cloning” is a classic example. This minimizes downtime to seconds but risks data inconsistency if the dirty block tracking fails. This method is simple, fast, and safe because