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
Invalid DRS Clusters
A cluster enabled for DRS becomes invalid (red) when the tree is no longer internally consistent, that is,
resource constraints are not observed.
The total amount of resources in the cluster does not aect whether the cluster is red. A cluster can be red,
even if enough resources exist at the root level, if there is an inconsistency at a child level.
You can resolve a red DRS cluster problem either by powering o one or more virtual machines, moving
virtual machines to parts of the tree that have sucient resources, or editing the resource pool seings in the
red part. Adding resources typically helps only when you are in the yellow state.
A cluster can also turn red if you recongure a resource pool while a virtual machine is failing over. A
virtual machine that is failing over is disconnected and does not count toward the reservation used by the
parent resource pool. You might reduce the reservation of the parent resource pool before the failover
completes. After the failover is complete, the virtual machine resources are again charged to the parent
resource pool. If the pool’s usage becomes larger than the new reservation, the cluster turns red.
If a user is able to start a virtual machine (in an unsupported way) with a reservation of 3GHz under
resource pool 2, the cluster would become red, as shown in the following gure.
Figure 11‑4. Red Cluster
cluster
Total Capacity: 12G
Reserved Capacity: 12G 15G
Available Capacity: 0G
RP1 (expandable)
Reservation: 4G
Reservation Used: 4G
Unreserved: 0G
RP2
Reservation: 2G
Reservation Used: 2G 5G
Unreserved: 0G
RP3 (expandable)
Reservation: 6G
Reservation Used: 2G
Unreserved: 4G 0G
VM1, 1G
VM7, 3G
VM2, 3G VM3, 1G VM4, 1G VM5, 1G VM6, 1G
Chapter 11 Using DRS Clusters to Manage Resources
VMware, Inc. 81