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
Create a DRS Cluster
When you add a host to a DRS cluster, the host’s resources become part of the cluster’s resources. In
addition to this aggregation of resources, with a DRS cluster you can support cluster-wide resource pools
and enforce cluster-level resource allocation policies.
The following cluster-level resource management capabilities are also available.
Load Balancing
The distribution and usage of CPU and memory resources for all hosts and
virtual machines in the cluster are continuously monitored. DRS compares
these metrics to an ideal resource utilization given the attributes of the
cluster’s resource pools and virtual machines, the current demand, and the
imbalance target. It then performs (or recommends) virtual machine
migrations accordingly. See “Virtual Machine Migration,” on page 65. When
you first power on a virtual machine in the cluster, DRS attempts to maintain
proper load balancing by either placing the virtual machine on an
appropriate host or making a recommendation. See “Admission Control and
Initial Placement,” on page 64.
Power management
When the vSphere Distributed Power Management (DPM) feature is
enabled, DRS compares cluster- and host-level capacity to the demands of
the cluster’s virtual machines, including recent historical demand. It places
(or recommends placing) hosts in standby power mode if sufficient excess
capacity is found or powering on hosts if capacity is needed. Depending on
the resulting host power state recommendations, virtual machines might
need to be migrated to and from the hosts as well. See “Managing Power
Resources,” on page 82.
Affinity Rules
You can control the placement of virtual machines on hosts within a cluster,
by assigning affinity rules. See “Using DRS Affinity Rules,” on page 86.
Prerequisites
You can create a cluster without a special license, but you must have a license to enable a cluster for vSphere
DRS (or vSphere HA).
Procedure
1 Right-click a data center in the vSphere Web Client and select New Cluster.
2 Name the cluster in the Name text box.
This name appears in the vSphere Web Client navigator.
3 Select the DRS Turn ON check box.
4 Select a default automation level for DRS.
Automation Level Action
Manual
n
Initial placement: Recommended host(s) is displayed.
n
Migration: Recommendation is displayed.
Partially Automated
n
Initial placement: Automatic.
n
Migration: Recommendation is displayed.
Fully Automated
n
Initial placement: Automatic.
n
Migration: Recommendation is executed automatically.
5 Set the migration threshold for DRS.
vSphere Resource Management
70 VMware, Inc.