Morpheus Native Migration Issue

[edmund01]

Windows MachineLinux Machine

So i have deployed the HVM Infrastructure with its Manager, did the initial configs (Group, Cloud, Cluster & all the way to intergrations with Alletra (Storage) & VMWare Cloud (for Migration Tests). Here's what's going on so far:

Deployment Summary:

• Morpheus HVM & Manager appliance has been deployed and is accessible [version: 9.0.1].
• The vSphere (vCenter) cloud has been integrated successfully, and existing workloads have been discovered/inventoried.
• The destination cluster/cloud has been configured, including networks, datastores and resource pools.

Issue: Migrations from vSphere Fail at "Create Destination Workloads"

When running migration plans from vSphere, the process completes the first stage successfully but stops at the second stage, "Create Destination Workloads", with the error: "Create Instance Failed"

This occurs for both Windows and Linux workloads, which suggests the problem is not OS-specific but related to how the destination instance is being provisioned.

Environment details:

• Morpheus version: 9.0.1
• Source: vCenter, ESXi version 7.0.3
• Destination: Morpheus, hvm-cloud & cluster.

Checks performed so far:

• Confirmed connectivity between the Morpheus appliance, vCenter and the destination hosts.
• Verified the destination network, datastore and resource pool selected in the migration plan are available and have sufficient capacity.

Kindly assist with:

• The likely root cause of the "Create Instance Failed" error at this stage.
• A workaround or configuration change that will allow us to move past this stage and complete the migrations.

Attached are screenshots (from both Migration Plans) with the error captured during the failed migration attempts.

Would appreciate insight on this as this is currently blocking further testing in the environment.

[CalvinZito]

Based on the documentation, the error occurring during "Create Destination Workloads" indicates the migration is failing when VM Essentials attempts to provision the target VM on the HVM cluster.

A few items to verify:

• Ensure all HVM hosts meet the migration prerequisites, including the required HVM Host Agent version and connectivity to vCenter/ESXi.
• Review the migration plan's network and datastore mappings. The documentation notes that destination networks and storage locations must be correctly mapped during migration plan creation.
• Verify the selected datastore is healthy, online, and available to the cluster hosts.
• Check Operations → Activity → History and Administration → Health → Morpheus Logs for the detailed provisioning error associated with the failed instance creation. The documentation specifically calls out these locations for provisioning and troubleshooting details.

Since the issue occurs with both Windows and Linux workloads, the documentation would suggest focusing first on destination cluster provisioning requirements, datastore availability, network configuration, and HVM host readiness rather than guest OS preparation.

If you can share the detailed message from the Migration History or Morpheus Logs, that will help narrow down the specific provisioning failure.

[추재은]

can you check if hvm host resolve esxi host fqdn?