vmWare ESXi 6.5 to Hyper-V conversion issues.

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

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

Post Reply
bhallman
Posts: 1
Joined: Mon Feb 19, 2024 10:03 pm

Mon Feb 19, 2024 10:58 pm

We have a VMware infrastructure that we are moving to Microsoft Hyper-V.
We tried the V2V converter and it "successfully" converted the VM and it showed up in Hyper-V, but it would not boot.

Testing methods:
Ran GUI version, selected "Remote VMware ESXi Server or vCenter" as source and Microsoft Hyper-V Server as destination. Result: Conversion successful, but corrupted VHDX.
Ran GUI version. Selected "Local File" as source and "Local File" as destination. Converted file as "VHDX pre-allocated image". Result: Conversion successful, but corrupted VHDX.
Ran GUI version. Selected "Local File" as source and "Local File" as destination. Converted file as "VHDX growable image". Result: Conversion successful, mountable volume. Was able to create a new VM in Hyper-V with the VHDX file and boot the server.
Performed same steps with the CLI version. If the destination format was pre-allocated, the resulting VHDX file would be corrupted and cannot be mounted, but would work if it was growable.

Is there any way to use the GUI method to do a direct V2V transfer and change the destination to growable when choosing VMware as the source and Hyper-V as the destination?
The workaround I was able to find would increase our migration time greatly as having the VM created automatically saves a great deal of time.
yaroslav (staff)
Staff
Posts: 2316
Joined: Mon Nov 18, 2019 11:11 am

Mon Feb 19, 2024 11:46 pm

Hi,

If conversion is successful, it seems that the problem is not with the V2V converter but the drivers the VM has connected to it or the Generation of the VM. Try converting the disks alone and creating the VM (boot from IDE controller).
Try removing the VMware tools from the VM before the conversion.
Post Reply