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 16‑1. Advanced Memory Attributes (Continued)
Attribute Description Default
Mem.MemZipMaxPct Specifies the maximum size of the compression cache in terms of the
maximum percentage of each virtual machine's memory that can be
stored as compressed memory.
10
LPage.LPageDefragEnable Enables large page defragmentation. 0 = disable. 1
LPage.LPageDefragRateVM Maximum number of large page defragmentation attempts per second
per virtual machine. Accepted values range from 1 to 1024.
32
LPage.LPageDefragRateTotal Maximum number of large page defragmentation attempts per second.
Accepted values range from 1 to 10240.
256
LPage.LPageAlwaysTryForNPT Try to allocate large pages for nested page tables (called 'RVI' by AMD
or 'EPT' by Intel). If you enable this option, all guest memory is backed
with large pages in machines that use nested page tables (for example,
AMD Barcelona). If NPT is not available, only some portion of guest
memory is backed with large pages. 0= disable.
1
Advanced NUMA Attributes
You can use the advanced NUMA attributes to customize NUMA usage.
Table 16‑2. Advanced NUMA Attributes
Attribute Description Default
Numa.RebalancePeriod Controls the frequency of rebalance periods, specified in
milliseconds. More frequent rebalancing can increase CPU
overheads, particularly on machines with a large number of
running virtual machines. More frequent rebalancing can also
improve fairness.
2000
Numa.MigImbalanceThreshold The NUMA rebalancer computes the CPU imbalance between
nodes, accounting for the difference between each virtual
machine’s CPU time entitlement and its actual consumption.
This option controls the minimum load imbalance between
nodes needed to trigger a virtual machine migration, in percent.
10
Numa.RebalanceEnable Enable NUMA rebalancing and scheduling. Set this option to 0
to disable all NUMA rebalancing and initial placement of virtual
machines, effectively disabling the NUMA scheduling system.
1
Numa.RebalanceCoresTotal Specifies the minimum number of total processor cores on the
host required to enable the NUMA rebalancer.
4
Numa.RebalanceCoresNode Specifies the minimum number of processor cores per node
required to enable the NUMA rebalancer.
This option and Numa.RebalanceCoresTotal are useful when
disabling NUMA rebalancing on small NUMA configurations (for
example, two-way Opteron hosts), where the small number of
total or per-node processors can compromise scheduling
fairness when you enable NUMA rebalancing.
2
vSphere Resource Management
VMware, Inc. 130