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
Cause
This may be because of problems with vMotion, DRS, or host compatibility. The following are the possible
reasons:
n
vMotion is not configured or enabled on this host.
n
DRS is disabled for the virtual machines on this host.
n
Virtual machines on this host are not compatible with any other hosts.
n
No other hosts have sufficient resources for any virtual machines on this host.
n
Moving any virtual machines from this host would violate a VM/VM DRS rule or VM/Host DRS rule.
n
DRS is disabled for one or more virtual machines on the host.
n
A device is mounted to the virtual machine.
Solution
Address the issues that are preventing DRS from moving virtual machines from the host.
Virtual Machine Problems
Virtual machine problems might cause DRS to not perform as expected.
Insucient CPU or Memory Resources
The virtual machine does not receive enough CPU or memory resources.
Problem
In some cases, the virtual machine's demand is greater than its resource entitlement. When this occurs,
the virtual machine doesn't receive enough CPU or memory resources.
Cause
The following sections describe the factors that influence the entitlement for a virtual machine.
Cluster is Yellow or Red If the cluster is yellow or red, the capacity is insufficient to meet the
resource reservations configured for all virtual machines and resource
pools in the cluster. The particular virtual machine might be one that is not
receiving its reservation. Check the status of the cluster (red or yellow) and
resolve the situation.
Resource Limit is Too
Restrictive
The virtual machine, its parent resource pool, or its resource pool ancestors
might have a configured resource limit that is too restrictive. Check whether
demand is equal to or greater than any configured limits.
vSphere Resource Management
VMware, Inc. 147