VirtualBox → Proxmox

VDIQCOW2

Convert VDI to QCOW2

VDI is VirtualBox’s native disk. People outgrow it when they want snapshots that Proxmox understands, or when a lab VM has to live next to VMware leftovers. QCOW2 is the common landing format on PVE.

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.

Talk to the AI — it replies
IACOPO

Describe what you want, then continue to convert.

VirtualBox is not VMware

A VDI is a different container from VMDK or VHDX. UUID, snapshot overlays and the VirtualBox.xml that sits beside the disk do not travel. We convert the disk file you upload.

If you actually have an OVA appliance, use the OVA guide — that is a tar of OVF plus disks, not a raw VDI.

Snapshots

A VDI that still depends on a snapshot overlay may not be a complete disk. Convert the merged disk. An incomplete chain fails with a diagnostic instead of a QCOW2 that looks plausible and boots garbage.

Isolation

The worker identifies VDI, converts in a disposable environment, validates QCOW2, then offers a download that expires. Densem is not datastore storage.

Questions

Can I keep VirtualBox snapshots?

No. QCOW2 can have its own snapshots later in Proxmox. VirtualBox overlay history does not come along.

Vagrant boxes?

If the payload is a VDI, this page applies. If it is an OVA or a cloud image, pick that format instead.

Same as RAW to QCOW2?

No. RAW is a flat image. VDI carries VirtualBox metadata. Wrong extension with the wrong bytes fails identification.