Issue migrating machines from vSphere

[hlago]

I am using the new migration tool, but when I try to migrate any machine from the vCenter infrastructure, I see the task “Export OVF template” in vCenter, but it does not progress.
What could be happening?
This happens with all the test machines I have set up in my VME test lab.

[Arnout_Verbeken]

I noticed in my environment that this is related to an ISO still being connected to the VM, or because the CD/DVD Drive is still pointing to a Datastore.
Make sure that the CD/DVD Drive is pointing to "Client Device" in the settings of the Vmware VM.

I hope this helps.

[hlago]

Thanks for the reply, but on the machines I’ve tested, the CD-ROM is either not active or doesn’t exist.

[Arnout_Verbeken]

It can also be related to vCenter naming resolution.

Is the vCenter FQDN reachable from the VME hosts?  (ping vcenterFQDN)
If not, add the FQDN to the VME hosts file.

Also take a look at the logs of the VME Manager during migration:

tail -f -n 500 /var/log/morpheus/morpheus-ui/current

after login to your VME Manager.

[hlago]

The name resolution from the VME hypervisors is correct.
The error message I see is the following.

[Arnout_Verbeken]

Look for logs about "migrationService".

[hlago]

I only see this, I have the VM Tools installed.
It also gets stuck on the “migration transfer action map” line, and in vCenter it looks like it’s trying to export to OVF but it doesn’t go past 0%.

[Arnout_Verbeken]

We can continue troubleshooting like this, but I think it will lead us to far and too much question/reply....

What kind of license are you using?

[hlago]

I`m using an NFR license.

Thank you for your help

[Arnout_Verbeken]

Please contact hpe-sw-trial-vmessentials@hpe.com

Kind Regards,

[kellysmith9312]

This issue usually occurs when the migration tool cannot fully communicate with vCenter or when export permissions are missing. Check the following:

• Confirm the account running the migration has the correct OVF/OVA export privileges.

• Verify there are no firewall or proxy rules blocking communication with vCenter.

• Make sure the migration tool version is compatible with your vSphere/vCenter release.

• Review the datastore and VM disk configuration since locked or thin-provisioned disks can stall exports.

We have resolved similar vSphere migration problems by validating permissions, updating tool versions, and adjusting vCenter roles. If you need help troubleshooting or performing a seamless migration, you can reach us here **Confidential information erased**