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
When a VM/VM DRS rule or VM/Host DRS rule is violated, it might be because DRS cannot move some or
all of the virtual machines in the rule. The reservation of the virtual machine or other virtual machines in the
anity rule, or their parent resource pools, might prevent DRS from locating all virtual machines on the
same host.
Solution
n
Check the DRS faults panel for faults associated with anity rules.
n
Compute the sum of the reservations of all the virtual machines in the anity rule. If that value is
greater than the available capacity on any host, the rule cannot be satised.
n
Compute the sum of the reservations of their parent resource pools. If that value is greater than the
available capacity of any host, the rule cannot be satised if the resources are obtained from a single
host.
Virtual Machine Power On Operation Fails
An error message appears stating that the virtual machine fails to power on.
Problem
The virtual machine fails to power on.
Cause
The virtual machine might fail to power on because of insucient resources or because there are no
compatible hosts for the virtual machine.
Solution
If the cluster does not have sucient resources to power on a single virtual machine or any of the virtual
machines in a group power-on aempt, check the resources required by the virtual machine against those
available in the cluster or its parent resource pool. If necessary, reduce the reservations of the virtual
machine to be powered-on, reduce the reservations of its sibling virtual machines, or increase the resources
available in the cluster or its parent resource pool.
DRS Does Not Move the Virtual Machine
DRS does not move the virtual machine when it is initially powered on despite insucient resources on the
host.
Problem
When you power on a virtual machine, DRS does not migrate it as expected when there are not enough
resources on the host where the virtual machine is registered.
Cause
The following are possible reasons why DRS does not move the virtual machine.
n
DRS is disabled on the virtual machine.
n
The virtual machine has a device mounted.
n
The virtual machine is not compatible with any other hosts.
n
No other hosts have a sucient number of physical CPUs or capacity for each CPU for the virtual
machine.
n
No other hosts have sucient CPU or memory resources to satisfy the reservations and required
memory of this virtual machine.
n
Moving the virtual machine will violate an anity or anti-anity rule.
Chapter 17 DRS Troubleshooting Information
VMware, Inc. 135