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
Fault Definitions 17
DRS faults indicate the reasons that prevent the generation of DRS actions (or the recommendation of
those actions in manual mode).
The DRS faults are defined within this section.
Note In this chapter, "Memory" can refer to physical RAM or Persistent Memory.
This chapter includes the following topics:
n
Virtual Machine is Pinned
n
Virtual Machine not Compatible with any Host
n
VM/VM DRS Rule Violated when Moving to another Host
n
Host Incompatible with Virtual Machine
n
Host Has Virtual Machine That Violates VM/VM DRS Rules
n
Host has Insufficient Capacity for Virtual Machine
n
Host in Incorrect State
n
Host Has Insufficient Number of Physical CPUs for Virtual Machine
n
Host has Insufficient Capacity for Each Virtual Machine CPU
n
The Virtual Machine Is in vMotion
n
No Active Host in Cluster
n
Insufficient Resources
n
Insufficient Resources to Satisfy Configured Failover Level for HA
n
No Compatible Hard Affinity Host
n
No Compatible Soft Affinity Host
n
Soft Rule Violation Correction Disallowed
n
Soft Rule Violation Correction Impact
VMware, Inc.
136