Virtual machine does not restart in HA failover in VMware vCenter Server 5.x

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• Virtual machine does not migrate to other hosts in the cluster when a HA failover event occurs.
• You see the event:
  
  Not enough resources to failover <VM_NAME> in <CLUSTER_NAME> in <DC_NAME>. vSphere HA will retry when resources become available.
  
  
• Despite the resource error message, the cluster has available resources for failover.
• Admission Control is enabled in the HA Cluster configuration.

Environment

VMware vCenter Server 5.1.x
VMware vCenter Server 5.5.x

Cause

This error may be caused by a network misconfiguration within the .vmx file.

Resolution

To resolve this issue:

1. Right-click the virtual machine that did not migrate to other host and click Edit Settings.
2. Determine whether the virtual machine network adapters are connected to a corresponding port group.
   
   Note: Any virtual machine network adapters that are not connected to a port group (standard or distributed) may cause the issue.
   
   
3. Select the proper port group for the network adapter of the virtual machine.

Note: This issue may also occur if the virtual machine has RDMs that are not available. To resolve this issue, verify and ensure that the there are no RDMs that are unavailable.

Additional Information

Virtual machine network adapters that are not connected to a port group may be caused by:

• The removal of the port group from the Standard/Distributed Switch
• Port group renaming

For more information, see vSphere High Availability Deployment Best Practices.