How to Import an OVA File into Proxmox VE

What Is an OVA File?

An OVA (Open Virtual Appliance) file is a single-file package containing a virtual machine. Inside, it holds an OVF descriptor (XML metadata about the VM's hardware configuration), one or more VMDK virtual disk files, and optionally a manifest for integrity verification. OVA files are commonly exported from VMware, VirtualBox, and other hypervisors. Proxmox VE can import them, but the process requires a few steps since Proxmox uses its own VM configuration format.

Method 1: Using qm importovf (Quick Path)

Proxmox provides the qm importovf command that handles most OVA imports automatically. First, extract the OVA, then import the OVF:

# Step 1: Upload the OVA to your Proxmox host
scp myvm.ova root@pve1:/tmp/

# Step 2: Extract the OVA (it's just a tar archive)
cd /tmp
tar xvf myvm.ova
# myvm.ovf
# myvm.vmdk
# myvm.mf (optional manifest)

# Step 3: Import using qm importovf
# Syntax: qm importovf   
qm importovf 110 /tmp/myvm.ovf local-lvm

# This creates VM 110 with the imported disk and
# basic settings from the OVF descriptor

After import, review and adjust the VM configuration:

# Check what was imported
qm config 110

# Common adjustments needed:
qm set 110 --scsihw virtio-scsi-pci   # Better SCSI controller
qm set 110 --net0 virtio,bridge=vmbr0  # VirtIO network adapter
qm set 110 --boot order=scsi0          # Set boot disk
qm set 110 --ostype l26                # Linux 2.6+ kernel (or win10, win11)
qm set 110 --agent enabled=1           # Enable QEMU guest agent

Method 2: Manual Conversion (Full Control)

Sometimes qm importovf does not parse the OVF correctly, or you want more control over the process. The manual method gives you full flexibility:

Step 1: Extract and Inspect

# Extract the OVA
tar xvf myvm.ova

# Check the disk format and size
qemu-img info myvm.vmdk
# image: myvm.vmdk
# file format: vmdk
# virtual size: 40 GiB
# disk size: 12.5 GiB

Step 2: Convert the Disk

Convert the VMDK to a format Proxmox handles natively. Choose qcow2 for flexibility (snapshots) or raw for maximum performance:

# Convert VMDK to qcow2 (supports snapshots and thin provisioning)
qemu-img convert -f vmdk -O qcow2 myvm.vmdk myvm.qcow2

# Or convert to raw (best performance, no snapshot support)
qemu-img convert -f vmdk -O raw myvm.vmdk myvm.raw

# For large disks, show progress
qemu-img convert -p -f vmdk -O qcow2 myvm.vmdk myvm.qcow2
# (45.00/100%)

Step 3: Create the VM and Import the Disk

# Create an empty VM shell
qm create 111 --name imported-vm --memory 4096 --cores 2 \
    --scsihw virtio-scsi-pci --net0 virtio,bridge=vmbr0

# Import the converted disk
qm importdisk 111 myvm.qcow2 local-lvm
# Output: Successfully imported disk as 'unused0:local-lvm:vm-111-disk-0'

Step 4: Attach and Configure the Disk

The imported disk appears as an unused disk. You need to attach it to a controller:

# Attach the unused disk to SCSI controller
qm set 111 --scsi0 local-lvm:vm-111-disk-0

# Set the boot order
qm set 111 --boot order=scsi0

# Add a display (if needed)
qm set 111 --vga qxl

# Add a cloud-init drive (optional, for cloud images)
# qm set 111 --ide2 local-lvm:cloudinit

Step 5: Start and Test

# Start the VM
qm start 111

# Open a console to verify it boots
qm terminal 111
# Or use the web UI console at https://pve1:8006

Handling Multi-Disk OVAs

Some OVA files contain multiple disks. Extract and convert each one:

# After extracting, you might see:
# myvm-disk1.vmdk
# myvm-disk2.vmdk

# Convert both
qemu-img convert -f vmdk -O qcow2 myvm-disk1.vmdk disk1.qcow2
qemu-img convert -f vmdk -O qcow2 myvm-disk2.vmdk disk2.qcow2

# Import both
qm importdisk 111 disk1.qcow2 local-lvm
qm importdisk 111 disk2.qcow2 local-lvm

# Attach both
qm set 111 --scsi0 local-lvm:vm-111-disk-0
qm set 111 --scsi1 local-lvm:vm-111-disk-1
qm set 111 --boot order=scsi0

Troubleshooting Common Issues

OVA imports do not always go smoothly. Here are the most common problems and fixes:

• VM does not boot – Check the boot order with qm config 111 | grep boot. The disk must be listed in the boot order. Also verify the BIOS type: some VMs need UEFI (qm set 111 --bios ovmf --efidisk0 local-lvm:1).
• No network connectivity – The original VM used a different NIC driver. Switch to VirtIO and install the appropriate drivers inside the guest.
• Slow performance – Replace IDE/SATA controllers with VirtIO SCSI. Install the QEMU guest agent for better integration.
• VMDK format not recognized – Some VMDKs use the ESXi sparse format. Try qemu-img convert -f vmdk -O qcow2 which handles most variants.
• Disk is split into multiple files (myvm-s001.vmdk, myvm-s002.vmdk) – Point qemu-img at the descriptor file (usually the smallest .vmdk), and it will read all extents automatically.

# Verify the VM is running correctly
qm status 111
qm agent 111 ping  # Tests guest agent connectivity

# Check for errors in the VM log
cat /var/log/qemu-server/111.log | tail -20

Clean Up

After a successful import and verification, remove the temporary files:

rm /tmp/myvm.ova /tmp/myvm.ovf /tmp/myvm.vmdk /tmp/myvm.qcow2 /tmp/myvm.mf

If you manage a fleet of imported VMs across multiple nodes, ProxmoxR gives you a quick way to check the status of all your VMs from your phone — useful for verifying that newly imported machines are running correctly without sitting at your desk.

Importing OVA files into Proxmox is reliable once you understand the two paths: qm importovf for quick imports and the manual convert-and-attach method when you need full control. Either way, always test the imported VM thoroughly before putting it into production.