Convert VHD to OVA

A VHD usually comes from Hyper-V or Microsoft Virtual PC, while an OVA is required when another hypervisor expects a complete appliance package. Converting the disk and rebuilding its virtual hardware lets you transfer, archive, or share the machine as one file.

What the VHD format is

VHD, or Virtual Hard Disk, is a file-based disk image containing an operating system, applications, partitions, and data. Microsoft Hyper-V, Virtual PC, Windows Disk Management, and some Azure workflows use VHD files.

A VHD can be fixed-size, dynamically expanding, or a differencing disk that depends on a parent VHD. It contains storage, not the complete virtual machine definition: CPU count, memory, firmware, network adapters, controllers, and other hardware settings are stored separately.

VHDX is a newer Microsoft disk format. It is not the same as VHD and may need conversion with Hyper-V, QEMU, or another disk utility before a VHD-based workflow can use it.

What the OVA format is

OVA is a single-file Open Virtualization Appliance package. It is a tar archive containing an OVF hardware descriptor, one or more virtual disks, and optionally a manifest containing checksums. The OVF descriptor can record virtual CPUs, memory, firmware, storage controllers, network adapters, and other machine settings.

OVA is convenient for importing or archiving a complete virtual machine because its configuration and disks travel together. VirtualBox, VMware products, and some cloud platforms can import OVA or OVF appliances, but their supported hardware settings differ.

OVA is not a compression format. Export commonly converts the VHD to VMDK and may require free space for the converted disk, the temporary VM, and the final archive. The OVA can therefore be as large as, or larger than, the source files.

Convert the VHD with VirtualBox

1. Install a current version of Oracle VirtualBox on a machine with enough free disk space. Keep the original VHD unchanged until the imported appliance has been tested.
2. Create a new VM in VirtualBox and select the operating-system family and version that match the guest. Choose Use an Existing Virtual Hard Disk File and attach the .vhd file.
3. Set memory and CPU count to values suitable for the source VM. Under Settings → System → Motherboard, enable EFI only when the original machine boots with UEFI. Hyper-V Generation 2 normally uses UEFI; Generation 1 normally uses legacy BIOS.
4. Check Settings → Storage and attach the disk to a controller supported by the guest, commonly SATA. The original Hyper-V controller configuration does not have to be reproduced exactly, but the guest must have a usable boot controller.
5. Start the VM and confirm that the operating system and applications work. Windows may install new virtual-hardware drivers, change the network interface, or request reactivation.
6. Shut down the guest completely. Do not export while the VHD is mounted by another VM, the host, or a backup process.
7. Choose File → Export Appliance, select the VM, set an output filename ending in .ova, and start the export. VirtualBox creates the OVF descriptor and packages the exported virtual disk, commonly as VMDK, inside the OVA.
8. On the destination system, choose File → Import Appliance, select the OVA, review its firmware, CPU, memory, controller, and network settings, then import it. Test the imported machine before deleting the VHD.

Use the VirtualBox command line

After creating and testing the VM, export it with:

VBoxManage export "VHD VM" --output "converted.ova"

Inspect the VM before export with:

VBoxManage showvminfo "VHD VM"

The command-line export requires a registered VirtualBox VM; it does not turn a bare VHD into a complete appliance without VM hardware settings. Create or configure that VM in the graphical interface, or use commands such as:

VBoxManage createvm --name "VHD VM" --ostype Windows10_64 --register
VBoxManage storagectl "VHD VM" --name SATA --add sata --controller IntelAhci
VBoxManage storageattach "VHD VM" --storagectl SATA --port 0 --device 0 --type hdd --medium "C:\VM\disk.vhd"

Set memory, CPUs, firmware, and the correct guest type before exporting. Replace the guest type when the source is not 64-bit Windows.

Other desktop workflows

For a disk-format conversion rather than a complete appliance conversion, qemu-img can convert a standalone VHD to VMDK:

qemu-img convert -p -f vpc -O vmdk source.vhd disk.vmdk

Create a VM around the resulting VMDK in VirtualBox or VMware, configure its firmware and hardware, then export it as OVA. StarWind V2V Converter is another desktop option for VHD-to-VMDK migration, especially in Hyper-V-to-VMware workflows, but it is not by itself a complete OVA exporter. VMware OVF Tool can package a correctly configured OVF and its disks into an OVA; it does not normally infer a full VM definition from a bare VHD.

Compatibility and quality limits

• Preserve differencing chains. A child VHD without its parent is incomplete. Merge or flatten the chain with the source virtualization platform before conversion, or provide the entire chain to a tool that supports it.
• Match firmware. A BIOS/UEFI mismatch can prevent booting even when the disk conversion succeeds. Secure Boot settings also may not transfer between hypervisors.
• Expect hardware changes. Hyper-V synthetic adapters, integration services, snapshots, storage controllers, and network identities may require cleanup or reconfiguration after import.
• Check guest licensing and drivers. Windows can detect different hardware, request reactivation, and install new storage or network drivers. Linux may require an initramfs or bootloader repair if the controller or firmware changes.
• Verify the archive after transfer. Use sha256sum converted.ova on Linux or Get-FileHash converted.ova in PowerShell, then import it on the target hypervisor and test the guest data.

Online conversion

General online file converters are unsuitable for this task: they would need to upload the guest's operating system and data, and most convert only disk images rather than create a valid OVF hardware definition. Use VirtualBox, QEMU, StarWind V2V, or VMware OVF Tool locally; use an online service only for non-sensitive test data when it explicitly documents VHD input and OVA appliance output.