Appliance → Proxmox
OVAQCOW2
An OVA is a tar: OVF descriptor, one or more disks, sometimes a manifest. Proxmox can import some appliances; many still fail on virtual hardware, multiple disks, or vendor-specific OVF. Pulling a QCOW2 out of the archive is the honest first step.
No account on the public uploader. Guest jobs stay within five conversions and 250 MB per day. Business rates start at €0.80/GB for OST → PST.
Describe what you want, then continue to convert.
Uploading an OVA is different from uploading a VMDK. We have to unpack the appliance, find the disk, and convert that disk to QCOW2. The OVF hardware section — CPU count, NICs, product URLs — is not replayed as a Proxmox VM.
If you only have a .vmdk already extracted, use VMDK to QCOW2 instead of wrapping it in an OVA for no reason.
Appliances with several VMDKs are a poor fit for a single guest download. The public converter targets the primary disk when that is unambiguous; messy multi-disk OVAs belong in Business.
Create a VM with the right firmware (SeaBIOS vs OVMF), import the QCOW2, attach it, then fix the network. That last mile is still yours — and it is why forum threads exist.
OVA is the packed appliance. A folder of .ovf plus .vmdk is not this upload. Pack it, or convert the VMDK directly.
They sit inside the disk. The converted QCOW2 still contains the guest OS. Uninstall vendor tools after first boot on Proxmox if they fight virtio.
We convert the disk bytes. We do not re-sign OVF manifests or preserve vendor EULAs as a Proxmox template.
