VCP550 · Question #50
An organization has a HA/DRS cluster containing a mixture of ESXi 4.1 and 5.5 hosts in the cluster. An ESXi 5.5 host has failed and HA attempted but failed to restart the virtual machines on another h
The correct answer is A. A virtual machine has an incompatible hardware version. In a mixed ESXi 4.1 and 5.5 cluster, HA restart will fail if a VM's hardware version requires ESXi 5.5 and no compatible host is available after the 5.5 host fails.
Question
An organization has a HA/DRS cluster containing a mixture of ESXi 4.1 and 5.5 hosts in the cluster. An ESXi 5.5 host has failed and HA attempted but failed to restart the virtual machines on another host. HA admission control is disabled. What condition could result in this behavior?
Options
- AA virtual machine has an incompatible hardware version
- BInsufficient resources exist on the remaining ESXi hosts
- CvMotion migration is not supported between ESXi 5.5 and 4.1 hosts
- DHA failover is not supported between ESXi 5.5 and 4.1 hosts
How the community answered
(50 responses)- A66% (33)
- B4% (2)
- C22% (11)
- D8% (4)
Why each option
In a mixed ESXi 4.1 and 5.5 cluster, HA restart will fail if a VM's hardware version requires ESXi 5.5 and no compatible host is available after the 5.5 host fails.
VMware VM hardware versions have a minimum ESXi host version requirement. A VM with hardware version 10 (introduced in vSphere 5.5) cannot be powered on by an ESXi 4.1 host, which only supports up to hardware version 7. When the only ESXi 5.5 host fails, HA attempts to restart those VMs on the remaining ESXi 4.1 hosts but fails due to this hardware version incompatibility, even with admission control disabled.
With admission control disabled, HA will still attempt VM restarts regardless of available resources; while resource exhaustion can cause power-on failures, the mixed-version cluster context points specifically to hardware version incompatibility as the cause.
HA restarts VMs by issuing a power-on operation on the target host - it does not use vMotion - so cross-version vMotion compatibility is entirely irrelevant to HA failover.
HA failover is not blocked between different ESXi versions per se; the failure condition is VM hardware version incompatibility with the target host, not a blanket restriction on cross-version HA.
Concept tested: HA restart failure due to VM hardware version incompatibility in mixed-version cluster
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.avail.doc/GUID-33A65FF7-DA22-4DC5-8B18-5A7F97CCA536.html
Topics
Community Discussion
No community discussion yet for this question.