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
Table 10‑1. Reservation Types
Reservation Type Description
Fixed The system checks whether the selected resource pool has sufficient unreserved resources. If
it does, the action can be performed. If it does not, a message appears and the action cannot
be performed.
Expandable
(default)
The system considers the resources available in the selected resource pool and its direct
parent resource pool. If the parent resource pool also has the Expandable Reservation
option selected, it can borrow resources from its parent resource pool. Borrowing resources
occurs recursively from the ancestors of the current resource pool as long as the Expandable
Reservation option is selected. Leaving this option selected offers more flexibility, but, at the
same time provides less protection. A child resource pool owner might reserve more resources
than you anticipate.
The system does not allow you to violate preconfigured Reservation or Limit settings. Each time you
reconfigure a resource pool or power on a virtual machine, the system validates all parameters so all
service-level guarantees can still be met.
Expandable Reservations Example 1
This example shows you how a resource pool with expandable reservations works.
Assume an administrator manages pool P, and defines two child resource pools, S1 and S2, for two
different users (or groups).
The administrator knows that users want to power on virtual machines with reservations, but does not
know how much each user will need to reserve. Making the reservations for S1 and S2 expandable
allows the administrator to more flexibly share and inherit the common reservation for pool P.
Without expandable reservations, the administrator needs to explicitly allocate S1 and S2 a specific
amount. Such specific allocations can be inflexible, especially in deep resource pool hierarchies and can
complicate setting reservations in the resource pool hierarchy.
Expandable reservations cause a loss of strict isolation. S1 can start using all of P's reservation, so that
no memory or CPU is directly available to S2.
Expandable Reservations Example 2
This example shows how a resource pool with expandable reservations works.
Assume the following scenario, as shown in the figure.
n
Parent pool RP-MOM has a reservation of 6GHz and one running virtual machine VM-M1 that
reserves 1GHz.
n
You create a child resource pool RP-KID with a reservation of 2GHz and with Expandable
Reservation selected.
n
You add two virtual machines, VM-K1 and VM-K2, with reservations of 2GHz each to the child
resource pool and try to power them on.
n
VM-K1 can reserve the resources directly from RP-KID (which has 2GHz).
vSphere Resource Management
VMware, Inc. 67