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
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.
n
RP2 was created with a reservation of 4GHz. Two virtual machines of 1GHz and 2GHz are powered
on (Reservation Used: 3GHz). 1GHz remains unreserved.
n
RP3 was created with a reservation of 3GHz. One virtual machine with 3GHz is powered on. No
resources for powering on additional virtual machines are available.
The following figure shows an example of a valid cluster with some resource pools (RP1 and RP3) using
reservation type Expandable.
Figure 12‑2. Valid Cluster with Expandable Resource Pools
cluster
Total Capacity: 16G
Reserved Capacity: 16G
Available Capacity: 0G
RP1 (expandable)
Reservation: 4G
Reservation Used: 6G
Unreserved: 0G
RP2
Reservation: 5G
Reservation Used: 3G
Unreserved: 2G
RP3 (expandable)
Reservation: 5G
Reservation Used: 5G
Unreserved: 0G
VM1, 2G
VM7, 2G
VM2, 2G
VM4, 1G VM8, 2G
VM3, 3G VM5, 2GVM6, 2G
A valid cluster can be configured as follows:
n
A cluster with total resources of 16GHz.
n
RP1 and RP3 are of type Expandable, RP2 is of type Fixed.
n
The total reservation used of the three resource pools combined is 16GHz (6GHz for RP1, 5GHz for
RP2, and 5GHz for RP3). 16GHz shows up as the Reserved Capacity for the cluster at top level.
n
RP1 was created with a reservation of 4GHz. Three virtual machines of 2GHz each are powered on.
Two of those virtual machines (for example, VM1 and VM7) can use RP1’s reservations, the third
virtual machine (VM6) can use reservations from the cluster’s resource pool. (If the type of this
resource pool were Fixed, you could not power on the additional virtual machine.)
vSphere Resource Management
VMware, Inc. 88