Convert QCOW2 to VHDX
Turn QCOW2 archives into VHDX. The whole disk, partitions and file systems included, block for block as a dynamically expanding VHDX for Hyper-V and Windows.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop QCOW2 files on the dialor turn it to pick what to do
A QEMU disk as a Hyper-V disk.The whole disk comes across as one VHDX file for Hyper-V and Windows.
What you get
One VHDX file that holds the whole disk, partitions and file systems included. It is copied block for block as a dynamically expanding VHDX.
Because the disk is copied as it is, what is on it stays as it was. Nothing is rebuilt or reorganized.
What it leaves behind
Internal snapshots are left out. Only the current state of the disk is written to the VHDX.
Some QCOW2 images are not supported. These are images that sit on a backing file, images that keep their data in a separate file, and encrypted images.
Going the other way
To move a disk from Hyper-V back to QEMU, use VHDX to QCOW2.
QCOW2 and VHDX.What each format is.
The formats
QEMU Disk
QEMU and KVM copy-on-write disk images.
- Extensions
- .qcow2 .qcow
- MIME type
- application
/x -qemu -disk - Kind
- Archives
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
In your code.The same QCOW2 to VHDX conversion through the API, for your app or your agent.
$ cv convert archive.qcow2 archive.vhdx$ cv convert archive.qcow2 archive.vhdxQuestions.What people ask about QCOW2 to VHDX.
Yes. The whole disk is copied block for block, so partitions and file systems come across with it.
No. Internal snapshots are left out of the VHDX.
No. Encrypted images are not supported. Images on a backing file or with data in a separate file are not supported either.
It is a dynamically expanding VHDX, made for Hyper-V and Windows.