StarWind Software

I have migrated serveral VMs from ESXi to Hyper-V that have a single disk with no issue. Ones that have multiple disks are failing. The VM starts, but only the C;\ is available. The message at the end of the migration seems to indicate that it succeeded, however when I open the new Hyper-V VM, the additional disks are not the there.

The log file shows this error:
ErrorCode = 32773;
ErrorDescription = "'TRMSRV' failed to add resources. (Virtual machine ID 888B2292-A801-4039-A3E4-CA8D9F48FB6A)\n\nCannot add 'E:\\VMs\\TRMSRV\\Virtual Hard Disks\\TRMSRV_.vhdx'. The disk is already connected to the virtual machine 'TRMSRV'. (Virtual machine ID 888B2292-A801-4039-A3E4-CA8D9F48FB6A)";
ErrorSummaryDescription = "'TRMSRV' failed to add resources to 'TRMSRV'.\n\nCannot add 'E:\\VMs\\TRMSRV\\Virtual Hard Disks\\TRMSRV_.vhdx'. The disk is already connected to the virtual machine 'TRMSRV'. (Virtual machine ID 888B2292-A801-4039-A3E4-CA8D9F48FB6A)";
HealthState = 5;

Try converting the disks alone and recreate the VM. It looks like something is going sideways with the config file.
See also this thread viewtopic.php?f=15&t=6763&p=36723&hilit=google#p36723 and https://drive.google.com/file/d/1hDP4gl ... Ea_5p/view

Thanks @yaroslav, but I think I sorted it another way.
The additional disks did get converted, but they weren't attached to the VM.

I went to Settings for the VM, selected the next drive, and pointed to the virtual disk file. Once the VM came up, I went to Disk Manager on the VM and brought the disks online. A bit of a manual process, but it worked.

Thanks for sharing your workaround. It looks like something went sideways with the VM config file. I am glad to read that you managed to sort it out.

Where is the "VM config file"?
I have done this conversion with several VM's, and had the same experience of missing the additional disks.

This is the VM configuration file. I doubt you can easily edit one for Hyper-V. You still can check the VMX file for an individual VM while the VM runs in ESXi.

Hi,

Thanks for your request, the issue should be ficed in the future build.