Convert VHDX to QCOW2
Turn VHDX archives into QCOW2. The whole disk, partitions and file systems included, block for block as a QCOW2 image (version 3) for QEMU, KVM and Proxmox.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop VHDX files on the dialor turn it to pick what to do
A Hyper-V disk as a QCOW2 image.The whole disk comes across as one file for QEMU, KVM and Proxmox.
What you get
One QCOW2 image, version 3, of the whole VHDX disk. Partitions and file systems are included, copied block for block.
The image is meant for QEMU, KVM and Proxmox, which read QCOW2 disk images.
What is not supported
Differencing disks that depend on a parent disk are not supported. The conversion needs a disk that stands on its own.
Disks whose log still holds changes that were never written into them are not supported either.
Going the other way
To move a QCOW2 image back to Hyper-V or Azure, use QCOW2 to VHDX. For other conversions with these formats, see every VHDX conversion.
VHDX and QCOW2.What each format is.
The formats
Hyper-V Disk
The newer Hyper-V and Azure disk images, made for disks over 2 TB.
- Extensions
- .vhdx
- MIME type
- application
/x -vhdx - Kind
- Archives
QEMU Disk
QEMU and KVM copy-on-write disk images.
- Extensions
- .qcow2 .qcow
- MIME type
- application
/x -qemu -disk - Kind
- Archives
In your code.The same VHDX to QCOW2 conversion through the API, for your app or your agent.
$ cv convert archive.vhdx archive.qcow2$ cv convert archive.vhdx archive.qcow2Questions.What people ask about VHDX to QCOW2.
Yes. The whole disk is copied block for block, partitions and file systems included.
No. A differencing disk depends on a parent disk, and that is not supported.
Version 3. It is meant for QEMU, KVM and Proxmox.
One file, the QCOW2 image of the disk.