StarWind Software

Hi

We are testing out the free tool to see if we can use it to migrate a bunch of VMs across from vmare to hyper-v scvmm 2019.

The process of converting the VM across went through with no errors, VM appears in SCVMM but when booting the VM, it displays the VM needs repairing with MS tools and will not boot.

Checked the disk and network settings are accurate compared to how it was setup in VMWare and everything looks correct.

Has anyone else experienced this issue where the new converted VM's wont boot and displays recovery on BIOS?

Thankyou

Welcome to StarWind Forum
Try uninstalling VMware Tools before conversion, and make sure to tick the repair mode checkbox when converting the disks.

yaroslav (staff) wrote: ↑

Fri Oct 04, 2024 5:21 pm

Welcome to StarWind Forum
Try uninstalling VMware Tools before conversion, and make sure to tick the repair mode checkbox when converting the disks.

Hi

Sorry for the late reply, busy weeks. Trying the above method did work and the VM booted up post migration.
However removing the vmware tools before hand causes the VMware VM to lose connectivity and become offline. Ideally we want to keep the old VM running until we failover to SCVMM.

Is this possible?

Thankyou

After migration try booting in safe mode or from an ISO and remove the drivers.

yaroslav (staff) wrote: ↑

Wed Oct 16, 2024 11:36 am

After migration try booting in safe mode or from an ISO and remove the drivers.

The reason I ask is we have a large VMware estate with over 2000 servers which we are looking at a POC to move to SCVMM due to VMware license cost increase.
Ideally we want the most efficient way to migrate VM's across with minimal downtime but having to either remove the vmware tools pre mirgation or spend time after migration by fixing boot up issues would be too much downtime per server if that makes sense.

I'll try testing booting into safe mode and or attaching the iso to see if it repairs.

Thankyou

Greetings,

Please log a call with us at support@starwind.com use this thread and 1230040 as your references.

Has anyone had better success using a script to automate the VMware Tools removal before the migration? Or maybe a different migration tool that handles drivers more gracefully? Appreciate any insights. Will log a call with support as well using the provided references.

It has to be done on the user side, not on the software side, as VMware tools not necessarily is a source of an issue. I'd view the issue in broad terms and connect it to the drivers or something within the VM that does not let it boot on the destination host.