6.5.1
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
- 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
- Index
Cluster is Overloaded
The cluster on which the virtual machine is running might have insucient
resources. Also, the virtual machine's share value is such that other virtual
machines are granted proportionally more of the resources. To determine the
demand is larger than the capacity, check the cluster statistics.
Host is Overloaded
To determine if the host's resources are oversubscribed, check the host
statistics. If they are oversubscribed, consider why DRS is not moving any of
the virtual machines now running on the host to other hosts. This condition
might exist for the following reasons:
n
The VM/VM DRS rules and VM/Host DRS rules require the current
virtual machine-to-host mapping. If such rules are congured in the
cluster, consider disabling one or more of them. Then run DRS and
check whether the situation is corrected.
n
DRS cannot move this virtual machine or enough of the other virtual
machines to other hosts to free up capacity. DRS will not move a virtual
machine for any of the following reasons:
n
DRS is disabled for the virtual machine.
n
A host device is mounted to the virtual machine.
n
Either of its resource reservations is so large that the virtual
machine cannot run on any other host in the cluster.
n
The virtual machine is not compatible with any other host in the
cluster.
Check whether any of these conditions exist for the virtual machine. If
none exist, the conditions might exist for other virtual machines in the
cluster. If this is the case, DRS cannot balance the cluster to address the
virtual machine's demand.
n
Decrease the DRS migration threshold seing and check whether the
situation is resolved.
n
Increase the virtual machine's reservation.
Solution
Address the problem that is causing the virtual machine to not receive enough CPU or memory resources.
VM/VM DRS Rule or VM/Host DRS Rule Violated
DRS rules specify which host a virtual machine must or must not reside on, or which virtual machines must
be or must not be on the same host.
Problem
A VM/VM DRS rule or a VM/Host DRS rule is violated.
Cause
VM/VM DRS rules specify that selected virtual machines should be placed on the same host (anity) or that
virtual machines be placed on dierent hosts (anti-anity). VM/Host DRS rules specify that selected virtual
machines should be placed on specied hosts (anity) or that selected virtual machines should not be
placed on specied hosts (anti-anity).
vSphere Resource Management
134 VMware, Inc.