Free online QCOW to OVA converter

A QCOW disk usually needs conversion when a desktop hypervisor or appliance importer accepts OVA but cannot open QEMU’s native image format. The conversion creates a portable virtual appliance containing the virtual disk and an OVF hardware description.

What the QCOW format is

QCOW, including the commonly used QCOW2 variant, is QEMU’s copy-on-write virtual disk format. QEMU and KVM commonly create it, and it is also used by libvirt-based virtualization platforms, OpenStack, Proxmox, and Linux virtualization tools.

A QCOW image stores guest operating-system data in allocated clusters rather than requiring the full virtual disk size immediately. QCOW2 supports features such as sparse allocation, snapshots, compression, and optional encryption. You typically encounter it when downloading a KVM appliance, exporting a QEMU virtual machine, or moving a VM from a Linux server.

What the OVA format is

OVA is a single-file package containing an OVF virtual-machine descriptor and one or more virtual disk images, usually VMDK files. VMware products, VirtualBox, and many appliance importers support OVA.

OVA is useful for distributing or archiving a complete virtual machine because its hardware settings, disk references, and metadata travel with the disk. It is a packaging format, not a disk-image format: the QCOW disk must normally be converted to a format accepted by the target hypervisor before it is placed in the OVA.

How to convert QCOW to OVA

Using QEMU and VirtualBox

1. Inspect the source image and confirm its actual format:
   qemu-img info source.qcow2
   Use the filename reported by your system; a QCOW image may use .qcow or .qcow2.
2. Convert the disk to VMDK with QEMU:

qemu-img convert -p -O vmdk source.qcow2 converted.vmdk

If automatic format detection is unsuitable, specify the source format explicitly, for example -f qcow2. Do not use -f qcow2 for an image identified as the older QCOW format.

3. Create a new virtual machine in VirtualBox with the guest operating system’s matching type and version. Choose Do not add a virtual hard disk when prompted.
4. Open the VM’s Settings → Storage, add a virtual hard disk, and select converted.vmdk. Match the original firmware setting under Settings → System → Motherboard: enable EFI for a UEFI guest and leave it disabled for a legacy BIOS guest.
5. Adjust the VM’s CPU count, memory, network adapter model, storage controller, and boot order to match the source environment. Start the VM and verify that the guest boots before exporting.
6. Power the guest off, then choose File → Export Appliance in VirtualBox. Select the VM, choose an output filename ending in .ova, review the appliance settings, and start the export.

The command-line equivalent is:

VBoxManage export "VM name" --output appliance.ova

Using a VMware-based workflow

Convert the QCOW image to VMDK with qemu-img, attach the VMDK to a newly created VMware VM with compatible firmware and controller settings, then export that VM as an OVF package and archive the OVF directory as a tar file ending in .ova. VMware’s OVF Tool can package an OVF directory, but it does not generally turn an arbitrary QCOW disk directly into a complete appliance.

Online conversion

For a small, non-sensitive image, you can use the free converter at 101convert.com without installing software. VM disks are often large and may contain credentials or private data, so local QEMU conversion is usually more suitable.

Compatibility and limitations

Block data is preserved during QCOW-to-VMDK conversion, but the virtual hardware is not. A guest may fail to boot if the exported appliance changes BIOS versus UEFI mode, disk-controller type, boot order, virtual CPU requirements, or network adapter model.

Shut down the guest cleanly before conversion. Converting a live QCOW image can capture an inconsistent filesystem unless the VM uses an appropriate snapshot or guest-consistent backup procedure.

QCOW snapshots, backing-file chains, compression, and encryption are not automatically reproduced as OVA features. Resolve or flatten backing files when necessary, and verify that the resulting VMDK contains all required data. The OVA itself is commonly an uncompressed tar archive, so packaging does not necessarily reduce disk size.

After export, test the OVA in the intended hypervisor. Check the appliance manifest if one is present; modifying files inside a signed OVA can invalidate its checksums. Keep the original QCOW image until the imported VM has booted and its applications and data have been verified.