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
If the cluster does not have sufficient resources to power on a single virtual machine, or any of the virtual
machines in a group power-on attempt, a message appears. Otherwise, for each virtual machine, DRS
generates a recommendation of a host on which to run the virtual machine and takes one of the following
actions
n
Automatically executes the placement recommendation.
n
Displays the placement recommendation, which the user can then choose to accept or override.
Note No initial placement recommendations are given for virtual machines on standalone hosts or in
non-DRS clusters. When powered on, they are placed on the host where they currently reside.
n
DRS considers network bandwidth. By calculating host network saturation, DRS is able to make
better placement decisions. This can help avoid performance degradation of virtual machines with a
more comprehensive understanding of the environment.
Single Virtual Machine Power On
In a DRS cluster, you can power on a single virtual machine and receive initial placement
recommendations.
When you power on a single virtual machine, you have two types of initial placement recommendations:
n
A single virtual machine is being powered on and no prerequisite steps are needed.
The user is presented with a list of mutually exclusive initial placement recommendations for the
virtual machine. You can select only one.
n
A single virtual machine is being powered on, but prerequisite actions are required.
These actions include powering on a host in standby mode or the migration of other virtual machines
from one host to another. In this case, the recommendations provided have multiple lines, showing
each of the prerequisite actions. The user can either accept this entire recommendation or cancel
powering on the virtual machine.
Group Power-on
You can attempt to power on multiple virtual machines at the same time (group power-on).
Virtual machines selected for a group power-on attempt do not have to be in the same DRS cluster. They
can be selected across clusters but must be within the same data center. It is also possible to include
virtual machines located in non-DRS clusters or on standalone hosts. These virtual machines are
powered on automatically and not included in any initial placement recommendation.
The initial placement recommendations for group power-on attempts are provided on a per-cluster basis.
If all the placement-related actions for a group power-on attempt are in automatic mode, the virtual
machines are powered on with no initial placement recommendation given. If placement-related actions
for any of the virtual machines are in manual mode, the powering on of all the virtual machines (including
the virtual machines that are in automatic mode) is manual. These actions are included in an initial
placement recommendation.
vSphere Resource Management
VMware, Inc. 70