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
Solution
There is no solution. If appropriate, disable vSphere HA before you attempt to put the host into
maintenance mode or standby mode.
DRS Does Not Move Any Virtual Machines onto a Host
DRS does not move any virtual machines onto a host.
Problem
DRS does not recommend migration of virtual machine to a host that has been added to a DRS-enabled
cluster.
Cause
After a host has been added to a DRS-enabled cluster, the virtual machines deployed to the host become
part of the cluster. DRS can recommend migration of some virtual machines to this host just added to the
cluster. If that does not occur, there may be problems with vMotion, host compatibility, or affinity rules.
The following are possible reasons:
n
vMotion is not configured or enabled on this host.
n
Virtual machines on other hosts are not compatible with this host.
n
The host does not have sufficient resources for any virtual machine.
n
Moving any virtual machines to this host would violate a VM/VM DRS rule or VM/Host DRS rule.
n
This host is reserved for HA failover capacity.
n
A device is mounted to the virtual machine.
n
The vMotion threshold is too high.
n
DRS is disabled for the virtual machines, hence the virtual machine could not be moved onto the
destination host.
Solution
Address the issue that prevents DRS from moving virtual machines onto a host.
DRS Does Not Move Any Virtual Machines from a Host
DRS does not move any virtual machines from a host.
Problem
Virtual machines are not moved from this host.
vSphere Resource Management
VMware, Inc. 146