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
No virtual machines on highly used hosts are moved to that host.
n
DPM is disabled on the host because of a user setting or host previously failing to exit standby.
Solution
Address that issue that prevents DRS from powering on the host.
Total Cluster Load Is Low
The total cluster load is low.
Problem
When the total cluster load is low, DRS does not power off the host.
Cause
The following are possible reasons why DRS does not power off the host:
n
Distributed Power Management (DPM) detected better candidates to power off.
n
vSphere HA needs extra capacity for failover.
n
The load is not low enough to trigger the host to power off.
n
DPM projects that the load will increase.
n
DPM is not enabled for the host.
n
DPM threshold is set too high.
n
While DPM is enabled for the host, no suitable power-on mechanism is present for the host.
n
DRS cannot evacuate the host.
n
The DRS migration threshold is at the highest setting and only performs mandatory moves.
Solution
Address the issue that is preventing DRS from powering off the host.
DRS Does Not Evacuate a Host Requested to Enter Maintenance
or Standby Mode
DRS does not evacuate a host requested to enter maintenance mode or standby mode.
Problem
When you attempt to put a host into maintenance or standby mode, DRS does not evacuate the host as
expected.
Cause
vSphere HA is enabled and evacuating this host might violate HA failover capacity.
vSphere Resource Management
VMware, Inc. 145