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 considering cluster validity scenarios, you should understand these terms.
Reservation
A xed, guaranteed allocation for the resource pool input by the user.
Reservation Used
The sum of the reservation or reservation used (whichever is larger) for each
child resource pool, added recursively.
Unreserved
This nonnegative number diers according to resource pool type.
n
Nonexpandable resource pools: Reservation minus reservation used.
n
Expandable resource pools: (Reservation minus reservation used) plus
any unreserved resources that can be borrowed from its ancestor
resource pools.
Valid DRS Clusters
A valid cluster has enough resources to meet all reservations and to support all running virtual machines.
The following gure shows an example of a valid cluster with xed resource pools and how its CPU and
memory resources are computed.
Figure 11‑1. Valid Cluster with Fixed Resource Pools
cluster
Total Capacity: 12G
Reserved Capacity: 11G
Available Capacity: 1G
RP1
Reservation: 4G
Reservation Used: 4G
Unreserved: 0G
RP2
Reservation: 4G
Reservation Used: 3G
Unreserved: 1G
RP3
Reservation: 3G
Reservation Used: 3G
Unreserved: 0G
VM1, 2G
VM7, 2G
VM2, 2G
VM4, 1G VM8, 2G
VM3, 3G VM5, 2GVM6, 2G
The cluster has the following characteristics:
n
A cluster with total resources of 12GHz.
n
Three resource pools, each of type Fixed (Expandable Reservation is not selected).
n
The total reservation of the three resource pools combined is 11GHz (4+4+3 GHz). The total is shown in
the Reserved Capacity eld for the cluster.
n
RP1 was created with a reservation of 4GHz. Two virtual machines. (VM1 and VM7) of 2GHz each are
powered on (Reservation Used: 4GHz). No resources are left for powering on additional virtual
machines. VM6 is shown as not powered on. It consumes none of the reservation.
vSphere Resource Management
78 VMware, Inc.