6.5.1
Table Of Contents
- vSphere Resource Management
- Contents
- About vSphere Resource Management
- Getting Started with Resource Management
- Configuring Resource Allocation Settings
- CPU Virtualization Basics
- Administering CPU Resources
- Memory Virtualization Basics
- Administering Memory Resources
- Configuring Virtual Graphics
- Managing Storage I/O Resources
- Managing Resource Pools
- Creating a DRS Cluster
- Using DRS Clusters to Manage Resources
- Creating a Datastore Cluster
- Initial Placement and Ongoing Balancing
- Storage Migration Recommendations
- Create a Datastore Cluster
- Enable and Disable Storage DRS
- Set the Automation Level for Datastore Clusters
- Setting the Aggressiveness Level for Storage DRS
- Datastore Cluster Requirements
- Adding and Removing Datastores from a Datastore Cluster
- Using Datastore Clusters to Manage Storage Resources
- Using NUMA Systems with ESXi
- Advanced Attributes
- Fault Definitions
- Virtual Machine is Pinned
- Virtual Machine not Compatible with any Host
- VM/VM DRS Rule Violated when Moving to another Host
- Host Incompatible with Virtual Machine
- Host Has Virtual Machine That Violates VM/VM DRS Rules
- Host has Insufficient Capacity for Virtual Machine
- Host in Incorrect State
- Host Has Insufficient Number of Physical CPUs for Virtual Machine
- Host has Insufficient Capacity for Each Virtual Machine CPU
- The Virtual Machine Is in vMotion
- No Active Host in Cluster
- Insufficient Resources
- Insufficient Resources to Satisfy Configured Failover Level for HA
- No Compatible Hard Affinity Host
- No Compatible Soft Affinity Host
- Soft Rule Violation Correction Disallowed
- Soft Rule Violation Correction Impact
- DRS Troubleshooting Information
- Cluster Problems
- Load Imbalance on Cluster
- Cluster is Yellow
- Cluster is Red Because of Inconsistent Resource Pool
- Cluster Is Red Because Failover Capacity Is Violated
- No Hosts are Powered Off When Total Cluster Load is Low
- Hosts Are Powered-off When Total Cluster Load Is High
- DRS Seldom or Never Performs vMotion Migrations
- Host Problems
- DRS Recommends Host Be Powered on to Increase Capacity When Total Cluster Load Is Low
- Total Cluster Load Is High
- Total Cluster Load Is Low
- DRS Does Not Evacuate a Host Requested to Enter Maintenance or Standby Mode
- DRS Does Not Move Any Virtual Machines onto a Host
- DRS Does Not Move Any Virtual Machines from a Host
- Virtual Machine Problems
- Cluster Problems
- Index
Host Has Insufficient Number of Physical CPUs for Virtual Machine
This fault occurs when the host hardware does not enough CPUs (hyperthreads) to support the number of
virtual CPUs in the virtual machine.
Host has Insufficient Capacity for Each Virtual Machine CPU
This fault occurs when the host does not have enough CPU capacity for running the virtual machine.
The Virtual Machine Is in vMotion
This fault occurs when DRS cannot move a virtual machine because it is in vMotion.
No Active Host in Cluster
This fault occurs when the cluster in which the virtual machine is being moved does not contain any hosts
that are connected and in a non-maintenance state.
This can occur, for example, when all the hosts are disconnected or in maintenance mode.
Insufficient Resources
This fault occurs when an aempted operation conicts with a resource conguration policy.
This fault may occur, for example, if a power-on operation reserves more memory than is allocated to a
resource pool.
Retry the operation after adjusting the resources to allow more memory.
Insufficient Resources to Satisfy Configured Failover Level for HA
This fault occurs when the HA conguration of CPU or memory resources reserved for failover is violated
or is insucient for the DRS operation.
This fault is reported when:
n
The host is requested to enter maintenance or standby mode.
n
The virtual machine violates failover when it aempts to power on.
No Compatible Hard Affinity Host
No host is available for the virtual machine that satises its mandatory VM/Host DRS anity or anti-anity
rules.
No Compatible Soft Affinity Host
No host is available for the virtual machine that satised its preferred VM/Host DRS anity or anti-anity
rules.
Soft Rule Violation Correction Disallowed
DRS migration threshold is set at mandatory-only.
This does not allow the generation of DRS actions to correct non-mandatory VM/Host DRS anity rules.
Chapter 16 Fault Definitions
VMware, Inc. 125