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
Power management.
Solution
Address the issues that are causing DRS to avoid performing vMotion migrations.
Host Problems
Host problems might cause DRS to not perform as expected.
DRS Recommends Host Be Powered on to Increase Capacity
When Total Cluster Load Is Low
The host must be powered on to help provide more capacity for the cluster or help hosts that are
overloaded.
Problem
DRS recommends that the host is powered on to increase capacity when the total cluster load is low.
Cause
The recommendation might be made because:
n
The cluster is a DRS-HA cluster. Additional powered-on hosts are needed to provide more failover
capability.
n
Some hosts are overloaded and virtual machines on currently powered-on hosts can be moved to
hosts in standby mode to balance the load.
n
The capacity is necessary to meet the MinPoweredOn{Cpu|Memory}Capacity advanced options.
Solution
Power on the host.
Total Cluster Load Is High
The total cluster load is high.
Problem
When the total cluster load is high, DRS does not power-on the host.
Cause
The following are possible reasons why DRS does not power-on the host:
n
VM/VM DRS rules or VM/Host DRS rules prevent the virtual machine from being moved to this host.
n
Virtual machines are pinned to their current hosts, so DRS cannot move these virtual machines to
hosts in standby mode to balance the load.
n
DRS or DPM is in manual mode and the recommendations were not applied.
vSphere Resource Management
VMware, Inc. 144