QuestionQ58

VerifiedManage Clusters in a Multicloud Environment

An administrator expanded a Nutanix cluster by adding repurposed nodes taken from a decommissioned cluster. The administrator confirmed the following:

  • The new nodes have the same number of cores, amount of memory, and amount of storage as the existing nodes
  • The new nodes are on the same subnet as the existing nodes
  • The new nodes are running the same version of AOS and AHV as the existing nodes

After adding the nodes, the administrator finds that VMs cannot be migrated to the newly added nodes.

What is the reason for this issue?

Explanation

AHV clusters support mixed CPU generations by constraining each VM's exposed virtual CPU features to the lowest common CPU generation present in the cluster, which allows live migration across hosts with different CPU generations. This CPU feature-set negotiation only occurs when a VM undergoes a full power cycle (power off, then power on) — a simple guest reboot does not trigger it. When repurposed nodes with a different CPU generation are added to a cluster, VMs that were powered on before the expansion retain the CPU feature set negotiated against the old cluster hardware. AHV will then block live migration of those VMs to the new nodes because their currently exposed CPU features are incompatible with the new hosts' CPUs, until the VMs are fully power-cycled so the hypervisor can renegotiate the correct, lowest-common-denominator CPU feature set.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!