When doing a conversion of a VM from VMware to Hyper-V, I've noticed that the current version (9.0.1.554) is cutting off the last character of the diskname. So if the disk in vmware is called "vmmigtest.vmdk" the converted VHDX is called "vmmigtes.vhdx". This isn't really an issue for VMs with a single disk, but I think this is the cause of why I'm having issues with converting VMs with multiple disks. In VMWare, if there are multiple disks, the second disk would be called "vmmigtest_1", third would be "vmmigtest_2" etc. However, during the conversion because it cuts off the last character they both end up trying to be named "vmmigtest_". Windows obviously doesn't allow this duplicate, so the third disk becomes "vmmigtest_(1)" on the file system.
When Starwind then tries to create the VM and attach the disks, I suspect it tries to mount the disks with the filenames of vmmigtes.vhdx, vmmigtest_.vhdx and vmmigtest_.vhdx and obviously fails because a) the two extra disks have the same name due to the character cut off and b) Windows has renamed the third disk with (1) at the end.
I'm not sure of a way to workaround this bug without modifying the VMs in VMware to be named uniquely at the start of their names so the cut off character at the end doesn't matter, or manually converting each extra disk and attaching them to the converted VM.
When Starwind then tries to create the VM and attach the disks, I suspect it tries to mount the disks with the filenames of vmmigtes.vhdx, vmmigtest_.vhdx and vmmigtest_.vhdx and obviously fails because a) the two extra disks have the same name due to the character cut off and b) Windows has renamed the third disk with (1) at the end.
I'm not sure of a way to workaround this bug without modifying the VMs in VMware to be named uniquely at the start of their names so the cut off character at the end doesn't matter, or manually converting each extra disk and attaching them to the converted VM.
Statistics: Posted by Matt_NZ — Mon Nov 25, 2024 11:15 pm