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
When you create a VM-Host affinity rule, its ability to function in relation to other rules is not checked. So
it is possible for you to create a rule that conflicts with the other rules you are using. When two VM-Host
affinity rules conflict, the older one takes precedence and the newer rule is disabled. DRS only tries to
satisfy enabled rules and disabled rules are ignored.
DRS, vSphere HA, and vSphere DPM never take any action that results in the violation of required affinity
rules (those where the virtual machine DRS group 'must run on' or 'must not run on' the host DRS group).
Accordingly, you should exercise caution when using this type of rule because of its potential to adversely
affect the functioning of the cluster. If improperly used, required VM-Host affinity rules can fragment the
cluster and inhibit the proper functioning of DRS, vSphere HA, and vSphere DPM.
A number of cluster functions are not performed if doing so would violate a required affinity rule.
n
DRS does not evacuate virtual machines to place a host in maintenance mode.
n
DRS does not place virtual machines for power-on or load balance virtual machines.
n
vSphere HA does not perform failovers.
n
vSphere DPM does not optimize power management by placing hosts into standby mode.
To avoid these situations, exercise caution when creating more than one required affinity rule or consider
using VM-Host affinity rules that are preferential only (those where the virtual machine DRS group 'should
run on' or 'should not run on' the host DRS group). Ensure that the number of hosts in the cluster with
which each virtual machine is affined is large enough that losing a host does not result in a lack of hosts
on which the virtual machine can run. Preferential rules can be violated to allow the proper functioning of
DRS, vSphere HA, and vSphere DPM.
Note You can create an event-based alarm that is triggered when a virtual machine violates a VM-Host
affinity rule. Add a new alarm for the virtual machine and select VM is violating VM-Host Affinity Rule
as the event trigger. For more information about creating and editing alarms, see the vSphere Monitoring
and Performance documentation.
vSphere Resource Management
VMware, Inc. 101