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
A similar result is obtained when determining Memory Shared and Memory Shared Common for the host.
n
Memory Shared for the host is the sum of each virtual machine's Memory Shared. Calculate shared
memory by looking at each virtual machine's guest physical memory and counting the number of
blocks that have arrows to machine memory blocks that themselves have more than one arrow
pointing at them. There are six such blocks in the example, so Memory Shared for the host is 24 KB.
n
Memory Shared Common is the amount of machine memory shared by virtual machines. To
determine common memory, look at the machine memory and count the number of blocks that have
more than one arrow pointing at them. There are three such blocks, so Memory Shared Common is
12 KB.
Memory Shared is concerned with guest physical memory and looks at the origin of the arrows. Memory
Shared Common, however, deals with machine memory and looks at the destination of the arrows.
The memory metrics that measure guest physical memory and machine memory might appear
contradictory. In fact, they are measuring different aspects of a virtual machine's memory usage. By
understanding the differences between these metrics, you can better use them to diagnose performance
issues.
Memory Reliability
Memory reliability, also known as error isolation, allows ESXi to stop using parts of memory when it
determines that a failure might occur, as well as when a failure did occur.
When enough corrected errors are reported at a particular address, ESXi stops using this address to
prevent the corrected error from becoming an uncorrected error.
Memory reliability provides better VMkernel reliability despite corrected and uncorrected errors in RAM. It
also enables the system to avoid using memory pages that might contain errors.
Correcting an Error Isolation Notification
With memory reliability, VMkernel stops using pages that receive an error isolation notification.
The user receives an event in the vSphere Client when VMkernel recovers from an uncorrectable memory
error, when VMkernel retires a significant percentage of system memory due to a large number of
correctable errors, or if there are a large number of pages that are unable to retire.
Procedure
1 Vacate the host.
2 Migrate the virtual machines.
3 Run memory related hardware tests.
About System Swap
System swap is a memory reclamation process that can take advantage of unused memory resources
across an entire system.
vSphere Resource Management
VMware, Inc. 45