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.
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software