Convert OVF to VHD

A Hyper-V host, Windows virtual-disk tool, or cloud service may require a VHD instead of an exported OVF appliance. The conversion extracts the virtual disk referenced by the OVF descriptor and changes that disk from VMDK to VHD; the OVF metadata is not converted into a VHD.

What the OVF format is

OVF, or Open Virtualization Format, is an XML-based description of a virtual machine or appliance. An OVF package commonly contains an .ovf descriptor, one or more virtual disks such as .vmdk files, and optionally a manifest with SHA checksums and certificate files.

VMware vSphere and Workstation, Oracle VirtualBox, and other hypervisors use OVF for appliance export and import. OVF is used when moving a preconfigured virtual machine between platforms, downloading an appliance, or restoring an exported machine. An .ova file is usually a single TAR archive containing the same package components.

What the VHD format is

VHD, or Virtual Hard Disk, is Microsoft’s virtual-disk format. Hyper-V, Virtual PC, Windows disk utilities, and some cloud platforms can use VHD files as virtual hard drives containing guest partitions and data.

VHD supports fixed-size and dynamically expanding disks, making it suitable when the destination accepts Microsoft virtual disks rather than OVF appliances or VMDK files. Its practical capacity limit is about 2 TiB; use VHDX for larger disks or newer Hyper-V deployments when the destination supports it.

How to convert the virtual disk

Using QEMU

1. Work on a copy of the package. If the source is an OVA, extract it with an archive utility or tar -xf appliance.ova.
2. Open the .ovf descriptor and inspect its File and Disk elements to identify each referenced VMDK. Select the VMDK descriptor, not an individual extent from a split disk set.
3. Install QEMU on Windows, Linux, or macOS, then inspect the source with qemu-img info source.vmdk. Resolve snapshots and backing files before conversion.
4. Create a dynamically expanding VHD with qemu-img convert -p -f vmdk -O vpc -o subformat=dynamic source.vmdk destination.vhd. Use -o subformat=fixed instead for a preallocated fixed VHD.
5. Check the output with qemu-img info destination.vhd, then attach it to the destination virtual machine as an existing disk.

For an appliance with multiple disks, convert every referenced VMDK separately and attach the resulting VHD files in the controller and device order specified by the OVF.

Using VirtualBox

VirtualBox can clone a readable VMDK into VHD format:

1. Extract the OVA if necessary and locate the VMDK named in the OVF descriptor.
2. Run VBoxManage clonemedium disk source.vmdk destination.vhd --format VHD.
3. Create or open the destination virtual machine and attach destination.vhd as an existing disk.

The graphical workflow varies by VirtualBox version. Where available, use VirtualBox Manager → Tools → Virtual Media Manager → Add to register the source VMDK, then clone it and select VHD as the output format.

Using a Windows conversion utility

StarWind V2V Converter provides a graphical VMDK-to-VHD workflow. Extract the OVF or OVA first, select the source VMDK, choose Microsoft VHD as the destination type, and select dynamic or fixed allocation. It converts the disk only; it does not reproduce the OVF appliance definition.

Online converters are usually unsuitable for this task. OVF packages can contain multi-gigabyte or confidential disks, and browser services commonly lack support for OVA archives, split VMDKs, multiple disks, backing chains, or VHD allocation choices. Use a local QEMU, VirtualBox, or StarWind workflow unless a trusted service explicitly supports the required VMDK-to-VHD operation and its upload limits and privacy terms are acceptable.

Compatibility limitations

• A manifest may contain checksums for the original VMDK. The converted VHD has different bytes, so the original manifest will not validate against it.
• Conversion changes the disk container, not the guest configuration. Recreate the source firmware mode, boot order, disk-controller type, and other required virtual hardware in the destination machine.
• A BIOS-installed guest may not boot in a UEFI-only machine. A guest configured for one controller type may also fail until the equivalent controller is provided.
• Snapshots, linked clones, and backing files must be consolidated or included as a complete chain. Converting only a dependent extent can create an incomplete disk.
• VHD output cannot exceed its format limit, and the destination platform may impose a smaller limit or require a particular VHD subtype.
• Boot a copy of the converted VHD and verify partitions, operating-system activation, network configuration, and application data before deleting the original package.