Convert VMDK to OVA

A hypervisor or appliance importer may require an OVA instead of a standalone VMware disk, especially when a virtual machine must be shared as one portable file. The conversion packages the VMDK together with the virtual machine’s hardware definition and import settings.

What VMDK contains

VMDK (Virtual Machine Disk) is a virtual hard-disk format developed by VMware and supported by VMware Workstation, ESXi, Fusion, VirtualBox, QEMU, and other virtualization software. It contains a guest operating system’s partitions and files, but normally does not contain the VM’s memory allocation, firmware choice, network configuration, controller type, or other hardware settings.

A VM can use one VMDK, a descriptor plus multiple extent files, or snapshot delta disks. Keep every referenced extent and snapshot file together; converting only one extent or delta disk can produce an incomplete or unbootable result.

What OVA contains

OVA (Open Virtualization Appliance) is a single TAR archive containing an OVF package. It normally includes an .ovf hardware and deployment descriptor, one or more virtual disks such as .vmdk, and optionally a manifest containing SHA checksums or certificate files. OVA is a package format, not a replacement virtual-disk format.

One file is easier to copy, archive, and import than a VM directory containing several disks and configuration files. OVA improves portability between supported hypervisors, but it does not guarantee identical hardware emulation or guest-driver behavior. OVA is not automatically smaller: its size depends on the exported disk format, allocated blocks, and compression or sparsity used by the exporter.

Convert with VMware OVF Tool

VMware OVF Tool is the most direct local method when the VMDK belongs to a VMware VM with a .vmx configuration file.

1. Shut down the guest operating system. Do not export a disk while it is being written to.
2. Consolidate or remove snapshots in VMware, or include all snapshot dependencies in the source VM.
3. Install the current OVF Tool from VMware and run:

ovftool /path/to/source.vmx /path/to/output.ova

For an ESXi or vCenter source, OVF Tool can export directly from an inventory URL, for example:

ovftool vi://user:password@esxi.example/VMName /path/to/output.ova

A standalone VMDK has no VM hardware definition for OVF Tool to export. Create a VM around the disk in VMware Workstation, Fusion, or another hypervisor first, then export the resulting .vmx VM.

Convert with VirtualBox

VirtualBox can attach an existing VMDK to a new VM and export that VM as an OVA.

1. Open VirtualBox and select New.
2. Set the guest OS family and version to match the installed system.
3. Choose Use an existing virtual hard disk file and select the VMDK descriptor file. If the disk is split, select the small descriptor file rather than an extent file.
4. Match the original VM’s firmware, storage controller, CPU count, memory, and network adapter where possible. Use EFI for a guest installed in UEFI mode; changing to BIOS can prevent booting.
5. Boot the VM once and confirm that the guest and its applications work, then shut it down.
6. Select File → Export Appliance, choose the VM, select an output path, and export it as .ova.

The equivalent command-line export is:

VBoxManage export VMName --output output.ova

VirtualBox’s export settings can add a manifest and can select OVF 2.0 where the destination supports it. OVF 1.0 is often the safer choice for older importers.

Online conversion and validation

Online file converters are generally unsuitable for this task. A full OVA requires VM metadata in addition to disk data, VMDK files can be very large, and uploading a disk exposes the guest’s files and credentials. Reputable general file-conversion services should not be assumed to support a complete VMDK-to-OVA appliance workflow. Use VMware OVF Tool or VirtualBox locally; use an online service only after verifying that it explicitly supports VM appliance packaging and the required privacy policy.

Inspect the result before transferring it:

tar -tf output.ova

The listing should contain an OVF descriptor and the expected disk files. Import the OVA into the target hypervisor and boot a copy, not the original VM. VMware OVF Tool can also validate an appliance with its verification options; an importer’s manifest check detects modified or incomplete package files.

Compatibility limitations

• Exporting usually does not preserve VMware snapshots, suspended memory state, encrypted-disk passwords, or every VMware-specific virtual device.
• The target hypervisor may change the disk controller, network adapter, MAC address, firmware, or virtual hardware version. The guest may require new storage or network drivers and may request reactivation.
• A disk created with thin provisioning or sparse extents may expand during export or import. Check the destination datastore capacity before starting.
• Do not rename a VMDK to .ova or place it in a TAR archive manually; that creates no OVF descriptor or hardware metadata.
• After the first boot, verify filesystem integrity, network configuration, time synchronization, application services, and licensing before deleting the source VM.