6.7
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
- Persistent Memory
- 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
n
Virtual machines are not compatible with the hosts to which DRS would move them. That is, at least
one of the hosts in the cluster is incompatible for the virtual machines that would be migrated. For
example, if host A's CPU is not vMotion-compatible with host B's CPU, then host A becomes
incompatible for powered-on virtual machines running on host B.
n
It would be more detrimental for the virtual machine's performance to move it than for it to run where it
is currently located. This may occur when loads are unstable or the migration cost is high compared
to the benefit gained from moving the virtual machine.
n
vMotion is not enabled or set up for the hosts in the cluster.
Solution
Address the problem that is causing the load imbalance.
Cluster is Yellow
The cluster is yellow due to a shortage of resources.
Problem
If the cluster does not have enough resources to satisfy the reservations of all resource pools and virtual
machines, but does have enough resources to satisfy the reservations of all running virtual machines,
DRS continues to run and the cluster is yellow.
Cause
A cluster can become yellow if the host resources are removed from the cluster (for example, if a host
fails).
Solution
Add host resources to the cluster or reduce the resource pool reservations.
Cluster is Red Because of Inconsistent Resource Pool
A DRS cluster becomes red when it is invalid. It may become red because the resource pool tree is not
internally consistent.
Problem
If the cluster resource pool tree is not internally consistent (for example, the sum of the children's
reservations is greater than the parent pool's nonexpandable reservation), the cluster does not have
enough resources to satisfy the reservations of all running virtual machines making the cluster red.
Cause
This can occur if vCenter Server is unavailable or if resource pool settings are changed while a virtual
machine is in a failover state.
Solution
Revert the associated changes or otherwise revise the resource pool settings.
vSphere Resource Management
VMware, Inc. 141