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
Figure 11‑1. Load Balancing
Host 1
VM1
VM4
VM2 VM3
VM5 VM6
Host 2
VM7
Host 3
VM8 VM9
Host 1
VM1 VM2 VM3
Host 2
VM7 VM4 VM5
Host 3
VM8 VM9 VM6
When a cluster becomes unbalanced, DRS makes recommendations or migrates virtual machines,
depending on the default automation level:
n
If the cluster or any of the virtual machines involved are manual or partially automated,
vCenter Server does not take automatic actions to balance resources. Instead, the Summary page
indicates that migration recommendations are available and the DRS Recommendations page
displays recommendations for changes that make the most efficient use of resources across the
cluster.
n
If the cluster and virtual machines involved are all fully automated, vCenter Server migrates running
virtual machines between hosts as needed to ensure efficient use of cluster resources.
Note Even in an automatic migration setup, users can explicitly migrate individual virtual machines,
but vCenter Server might move those virtual machines to other hosts to optimize cluster resources.
By default, automation level is specified for the whole cluster. You can also specify a custom automation
level for individual virtual machines.
DRS Migration Threshold
The DRS migration threshold allows you to specify which recommendations are generated and then
applied (when the virtual machines involved in the recommendation are in fully automated mode) or
shown (if in manual mode). This threshold is also a measure of how much cluster imbalance across host
(CPU and memory) loads is acceptable.
vSphere Resource Management
VMware, Inc. 72