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
Host has Insucient Capacity for Virtual Machine
This fault occurs when the host does not have enough CPU or memory capacity for running the virtual
machine.
Host in Incorrect State
This fault occurs when the host is entering maintenance or standby state when needed for DRS action to
occur.
To address this fault, cancel the request for the host to enter standby or maintenance mode.
Host Has Insucient Number of Physical CPUs for Virtual
Machine
This fault occurs when the host hardware does not enough CPUs (hyperthreads) to support the number
of virtual CPUs in the virtual machine.
Host has Insucient Capacity for Each Virtual Machine
CPU
This fault occurs when the host does not have enough CPU capacity for running the virtual machine.
The Virtual Machine Is in vMotion
This fault occurs when DRS cannot move a virtual machine because it is in vMotion.
No Active Host in Cluster
This fault occurs when the cluster in which the virtual machine is being moved does not contain any hosts
that are connected and in a non-maintenance state.
This can occur, for example, when all the hosts are disconnected or in maintenance mode.
Insucient Resources
This fault occurs when an attempted operation conflicts with a resource configuration policy.
This fault may occur, for example, if a power-on operation reserves more memory than is allocated to a
resource pool.
Retry the operation after adjusting the resources to allow more memory.
vSphere Resource Management
VMware, Inc. 138