Migration Vmware to Hyper-V

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

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

Post Reply
Lehn_MR
Posts: 4
Joined: Tue Dec 10, 2024 6:05 pm

Tue Dec 10, 2024 6:21 pm

Hello,

I have a problem during the boot with a VM after converting it from Vmware to Hyper-V.
The machine is a Red-Hat 7.5 and this following erreurs display :

Code: Select all

/dev/mapper/rhel-root does not exist
/dev/rhel/root does not exist
/dev/rhel/swap does not exist
I have already tried to regenerate the dracut to solve the problem but it doesn't change anything...
Below the command that i've tried :

Code: Select all

 dracut -f -v --regenerate-all 
I've tried to add the following parameter in the /etc/dracut.conf :

Code: Select all

add_drivers+=" hid_hyperv hv_utils hv_vmbus hv_storvsc hv_netsvc"
But it doesn't change anything too

The rescue mode start without any problem.

Can you help me to solve this problem please?
yaroslav (staff)
Staff
Posts: 3598
Joined: Mon Nov 18, 2019 11:11 am

Tue Dec 10, 2024 8:20 pm

Welcome to StarWind Forum. Can you please convert an individual disk and recreate the VM using that disk?
Use repair mode checkbox if possible.
Lehn_MR
Posts: 4
Joined: Tue Dec 10, 2024 6:05 pm

Wed Dec 11, 2024 10:05 am

Hello,

Thanks for your answer.
I tried your method but I had the same result during the VM boot.
During the conversion, I checked the Repair mode but it didn't work and returned an error.

Do you have any others ideas ?
yaroslav (staff)
Staff
Posts: 3598
Joined: Mon Nov 18, 2019 11:11 am

Wed Dec 11, 2024 11:47 am

Hi,

You are always welcome!
Do you have VMware tools installed into that VM?
Lehn_MR
Posts: 4
Joined: Tue Dec 10, 2024 6:05 pm

Wed Dec 11, 2024 1:46 pm

Hello

Yes, VMware Tools is install into the VM.
yaroslav (staff)
Staff
Posts: 3598
Joined: Mon Nov 18, 2019 11:11 am

Wed Dec 11, 2024 2:14 pm

Thanks for your feedback.
Can you try uninstalling them prior to conversion?
The error you point out seems to be some sort of a driver mismatch.
As a last resort, you can try converting the VM to OVF and moving it to the destination.
Lehn_MR
Posts: 4
Joined: Tue Dec 10, 2024 6:05 pm

Fri Dec 13, 2024 8:30 am

Hello,

I tried too but it did'nt work too, the same erreur appear during the boot.
To solve my problem, I reinstall from scratch the VM directly in the HyperV environment and everything work now.

Thanks again for your help
yaroslav (staff)
Staff
Posts: 3598
Joined: Mon Nov 18, 2019 11:11 am

Fri Dec 13, 2024 2:52 pm

Sorry to read that there was no simple workaround.
Thanks for sharing your experience.
Post Reply