6.0.1
Table Of Contents
- vSphere Resource Management
- Contents
- About vSphere Resource Management
- Updated Information
- Getting Started with Resource Management
- Configuring Resource Allocation Settings
- CPU Virtualization Basics
- Administering CPU Resources
- Memory Virtualization Basics
- Administering Memory Resources
- View Graphics Information
- 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
Overcommitted DRS Clusters
A cluster becomes overcommitted (yellow) when the tree of resource pools and virtual machines is
internally consistent but the cluster does not have the capacity to support all resources reserved by the child
resource pools.
There will always be enough resources to support all running virtual machines because, when a host
becomes unavailable, all its virtual machines become unavailable. A cluster typically turns yellow when
cluster capacity is suddenly reduced, for example, when a host in the cluster becomes unavailable. VMware
recommends that you leave adequate additional cluster resources to avoid your cluster turning yellow.
Figure 11‑3. Yellow Cluster
X
cluster
Total Capacity: 12G 8G
Reserved Capacity: 12G
Available Capacity: 0G
RP1 (expandable)
Reservation: 4G
Reservation Used: 4G
Unreserved: 0G
RP2
Reservation: 5G
Reservation Used: 3G
Unreserved: 2G
RP3 (expandable)
Reservation: 3G
Reservation Used: 3G
Unreserved: 0G
VM1, 2G
VM7, 0G
VM2, 2G
VM4, 1G
VM3, 3G VM5, 5GVM6, 2G
In this example:
n
A cluster with total resources of 12GHz coming from three hosts of 4GHz each.
n
Three resource pools reserving a total of 12GHz.
n
The total reservation used by the three resource pools combined is 12GHz (4+5+3 GHz). That shows up
as the Reserved Capacity in the cluster.
n
One of the 4GHz hosts becomes unavailable, so total resources reduce to 8GHz.
n
At the same time, VM4 (1GHz) and VM3 (3GHz), which were running on the host that failed, are no
longer running.
n
The cluster is now running virtual machines that require a total of 6GHz. The cluster still has 8GHz
available, which is sufficient to meet virtual machine requirements.
The resource pool reservations of 12GHz can no longer be met, so the cluster is marked as yellow.
vSphere Resource Management
80 VMware, Inc.