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
Cluster Is Red Because Failover Capacity Is Violated
A DRS cluster becomes red when it is invalid. It may become red because failover capacity is violated.
Problem
The cluster attempts to fail over virtual machines if there is host failure, but is not guaranteed to have
enough resources available to fail over all virtual machines covered by the failover requirements.
Cause
If a cluster enabled for HA loses so many resources that it can no longer fulfill its failover requirements, a
message appears and the cluster's status changes to red.
Solution
Review the list of configuration issues in the yellow box at the top of the cluster Summary page and
address the issue that is causing the problem.
No Hosts are Powered O When Total Cluster Load is Low
Hosts are not powered off when the total cluster load is low.
Problem
Hosts are not powered off when the total cluster load is low because extra capacity is needed for HA
failover reservations.
Cause
Hosts might not be powered off for the following reasons:
n
The MinPoweredOn{Cpu|Memory}Capacity advanced options settings need to be met.
n
Virtual machines cannot be consolidated onto fewer hosts due to their resource reservations,
VM/Host DRS rules, VM/VM DRS rules, not being DRS-enabled, or not being compatible with the
hosts having available capacity.
n
Loads are unstable.
n
DRS migration threshold is at the highest setting and only allows mandatory moves.
n
vMotion is unable to run because it is not configured.
n
DPM is disabled on the hosts that might be powered off.
n
Hosts are not compatible for virtual machines to be moved to another host.
n
Host does not have Wake On LAN, IPMI, or iLO technology. Either one is required for DPM to enter a
host in standby.
Solution
Address the issue that prevents hosts from being powered off when the total cluster load is low.
vSphere Resource Management
VMware, Inc. 142