6.0.1
Table Of Contents
- vSphere Resource Management
- Contents
- About vSphere Resource Management
- Updated Information
- Getting Started with Resource Management
- Configuring Resource Allocation Settings
- CPU Virtualization Basics
- Administering CPU Resources
- Memory Virtualization Basics
- Administering Memory Resources
- View Graphics Information
- 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
Cause
DRS never performs vMotion migrations when one or more of the following issues is present on the cluster.
n
DRS is disabled on the cluster.
n
The hosts do not have shared storage.
n
The hosts in the cluster do not contain a vMotion network.
n
DRS is manual and no one has approved the migration.
DRS seldom performs vMotion when one or more of the following issues is present on the cluster:
n
Loads are unstable, or vMotion takes a long time, or both. A move is not appropriate.
n
DRS seldom or never migrates virtual machines.
n
DRS migration threshold is set too high.
DRS moves virtual machines for the following reasons:
n
Evacuation of host that a user requested enter maintenance or standby mode.
n
VM/Host DRS rules or VM/VM DRS rules.
n
Reservation violations.
n
Load imbalance.
n
Power management.
Solution
Address the issues that are causing DRS to avoid performing vMotion migrations.
Host Problems
Host problems might cause DRS to not perform as expected.
DRS Recommends Host be Powered On to Increase Capacity When Total
Cluster Load Is Low
The host should be powered on to help provide more capacity for the cluster or help hosts that are
overloaded.
Problem
DRS recommends that the host be powered on to increase capacity when the total cluster load is low.
Cause
The recommendation might be made because:
n
The cluster is a DRS-HA cluster. Additional powered-on hosts are needed in order to provide more
failover capability.
n
Some hosts are overloaded and virtual machines on currently powered-on hosts can be moved to hosts
in standby mode to balance the load.
n
The capacity is needed to meet the MinPoweredOn{Cpu|Memory}Capacity advanced options.
Solution
Power on the host.
vSphere Resource Management
130 VMware, Inc.