All VirtualBox conversions to HyperV create corrupted vhdx files

VM image converter (VMDK, VHD, VHDX, IMG, RAW, QCOW and QCOW2), P2V migrator

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
BD9999
Posts: 5
Joined: Mon Jun 10, 2024 12:39 am

Tue Jun 11, 2024 6:35 am

I'm in a pickle here and don't know what to do: Either all of my VirtualBox (Version 7.0.12 r159484 (Qt5.15.2)) machines are corrupted or something is wrong with the V2V conversion process or HyperV has an issue.
This seems to only happen when doing a direct conversion: logging into VBox, choosing the drive, selecting & logging into HyperV, then the conversion starts and completes seemingly everything perfectly.
When I try to boot the newly created HyperV, it says the vhdx file is corrupted. Same if I attempt to mount it in Explorer.
I did figure out, after more experiments, that the vdi to vhdx conversion is the culprit. If I directly point to the vdi file (local file) and do the conversion to (local file), the vhdx is corrupted right off the bat. I tried this with Win10, and same result: corrupted vhdx file, then again with an Ubuntu vdi to vhdx -> corrupted file.
vdi to vhd works fine (disk image is not corrupted).
I see many others seem to have this same problem. I'll just manually convert the vhd to vhdx with HyperV's tool for now.
yaroslav (staff)
Staff
Posts: 2447
Joined: Mon Nov 18, 2019 11:11 am

Tue Jun 11, 2024 7:56 am

Hi,

Do you see the corruption when you boot the VM or is it the hypervisor screaming about disk corruption?
If the latter is true see this thread viewtopic.php?f=15&t=6763&p=36723&hilit=google#p36723 and https://drive.google.com/file/d/1hDP4gl ... sp=sharing
BD9999
Posts: 5
Joined: Mon Jun 10, 2024 12:39 am

Tue Jun 11, 2024 6:24 pm

The latter (HV - same message as in post you referenced).
I found a link in that thread for another V2V version on the google drive and will try that version today. Thanks!
yaroslav (staff)
Staff
Posts: 2447
Joined: Mon Nov 18, 2019 11:11 am

Tue Jun 11, 2024 9:58 pm

Great to read you solved it.
We are working on the fix. Thanks for your patience and cooperation.
Post Reply