Issue/Introduction

This article helps troubleshoot failures to create a target host instance during ZSphere migration.

Symptoms

• The migration task fails while creating the target VM instance.
• The logs indicate that host architectures do not match. For example, the target cluster contains both ARM and x86 hosts.

Environment

• Product: ZVF
• Version: 4.10.x
• Component: ZMigrate
• Affected object: migration service
• Scenario: For migration and cloning issues, confirm the current version, deployment type, storage type, and operation timeline.

Possible causes

• The target cluster contains mixed CPU architectures, and the migration task selects an incompatible host.
• The source image architecture, target cluster architecture, and migration tool identification result are inconsistent.
• Target cluster resource filtering or scheduling constraints are insufficient, causing the migration request to be placed on a node with the wrong architecture.

Remediation

Perform the following checks in order, and record the affected object, occurrence time, complete error message, and current status.

1. Confirm the source VM CPU architecture, operating system architecture, and host architecture of the target ZSphere cluster.
2. Check whether the target cluster contains both ARM and x86 hosts. During migration, specify a cluster or target host with the same architecture.
3. Review the scheduling reason and hostUuid for the VM creation failure in the management service logs.
4. Before migration, manually create a test VM with the same specifications in the target cluster to verify architecture and image compatibility.

Resolution

1. Restrict the migration target to a CPU architecture cluster or host that is compatible with the source VM.
2. In a heterogeneous cluster, group resources before starting the migration again.

Verification

• The target cluster can create a test VM with the same specifications.
• The migration task can create the target host instance and continue.