After migration to Hyper-V, VM won't start

[f8tech]

Last night, after the V2V Converter successfully migrated the VM from VMware ESXi to a new Hyper-V host I attempted to power on the virtual server from Hyper-V Manager. But it failed to start. I attached a screenshot of the error to this post.

What went wrong? Is this issue with the migration of the VM able to be resolved?

[yaroslav (staff)]

Get the V2V converter from this thread viewtopic.php?f=15&t=6317&p=36548&hilit=google#p36548.

[f8tech]

Let me see if I understand you. So, I need to delete the migrated VM folders from the Hyper-V host that was migrated. Uninstall the new version of V2V Converter. Then download and install the older version of V2V Converter from the Google Drive link. Then run the migration again. Is that correct?

[yaroslav (staff)]

Hi,

Yes, give it a try. Let me know if that helps. Can you please let me know which version of the converter you currently use?

[f8tech]

The newest one. I just downloaded and installed it on 5/1. It's shows it is version 9.0.1.444

[yaroslav (staff)]

Thanks for your update. Yes, please try the older version.

[asavchenko]

Hello @yaroslav,

first thank you for this helpful tool

i have same Problem
I am not a QA ^^, but I will try to describe the problem in my case in detail
so,
9.0.1.544

1. same Problem for Linux VM (AlmaLinux 9 XFS/LVM UEFI VM Gen 2) (2 Disks, first 50GB, second 250GB) VMware to Hyper-V (vmdk to vhdx), conversion is successful, but problem only with second disk (like on screenshot in this topic), VM not started
and plus the converted VHDX files is missing the last character in the file name, but it no problem

9.0.1.509

2. Linux VM (AlmaLinux 9 XFS/LVM UEFI VM Gen 2) (but only 1 Disk 50GB) VMware to Hyper-V (vmdk to vhdx), conversion is successful, no problem
and plus the converted VHDX file is missing the last character in the file name, but it no problem, VM stated without Problem

3. Windows VM (Windows 2012/2016/2019/2022 NTFS UEFI VM Gen 2) (1 Disk VM 90GB) VMware to Hyper-V (vmdk to vhdx), conversion is successful, no problem
and plus the converted VHDX file is missing the last character in the file name, but it no problem, VM stated without Problem

4. Windows VM (Windows 2012/2016/2019/2022 NTFS UEFI VM Gen 2) (3 Disk VM first 90GB, second 1TB , third 1,5TB ) VMware to Hyper-V (vmdk to vhdx), conversion is not successful because the converted VHDX files is missing the last character in the file name and 2 Disks (first and third) have same name
conversion for only third disk is successful, VM stated without Problem

so, i converted first Linux VM with 9.0.1.268 without Problem and VHDX files have all characters

Can you please release a fix for new Version of Converter

Thanks and Regards

[yaroslav (staff)]

Thanks for your update and such a detailed description. I will pass this information to my colleagues.
We are aware of the issue and my colleagues are working on a resolution.

[Tomasz]

Team,
do you have any estimated release date for the new release with the above issue fixed?

Tomasz

[yaroslav (staff)]

Hi,

Sadly no. Please use the previous converter version.

[Tomasz]

Can you provide the link for the last working one?

[yaroslav (staff)]

Hi,

Sharing one from the thread above (it works https://drive.google.com/file/d/1hDP4gl ... sp=sharing)

[Beata55]

Last night, after the V2V Converter successfully migrated the VM from VMware ESXi to a new Hyper-V host I attempted to power on the virtual server from Hyper-V Manager. But it failed to start. I attached a screenshot of the error to this post.

What went wrong? Is this issue with the migration of the VM able to be resolved?

Try checking the VM's configuration in Hyper-V (like network adapters or virtual hardware versions) Also, confirm the VM's configuration files are intact. If needed, try to rebuild the VM on Hyper-V manually or use the Hyper-V "Import" feature to reconfigure the VM.

[yaroslav (staff)]

It is a known issue. Working on the fix.