6.0.1
Table Of Contents
- vSphere Resource Management
- Contents
- About vSphere Resource Management
- Updated Information
- Getting Started with Resource Management
- Configuring Resource Allocation Settings
- CPU Virtualization Basics
- Administering CPU Resources
- Memory Virtualization Basics
- Administering Memory Resources
- View Graphics Information
- 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
Measuring and Differentiating Types of Memory Usage
The Performance tab of the vSphere Web Client displays a number of metrics that can be used to analyze
memory usage.
Some of these memory metrics measure guest physical memory while other metrics measure machine
memory. For instance, two types of memory usage that you can examine using performance metrics are
guest physical memory and machine memory. You measure guest physical memory using the Memory
Granted metric (for a virtual machine) or Memory Shared (for a host). To measure machine memory,
however, use Memory Consumed (for a virtual machine) or Memory Shared Common (for a host).
Understanding the conceptual difference between these types of memory usage is important for knowing
what these metrics are measuring and how to interpret them.
The VMkernel maps guest physical memory to machine memory, but they are not always mapped one-to-
one. Multiple regions of guest physical memory might be mapped to the same region of machine memory
(in the case of memory sharing) or specific regions of guest physical memory might not be mapped to
machine memory (when the VMkernel swaps out or balloons guest physical memory). In these situations,
calculations of guest physical memory usage and machine memory usage for an individual virtual machine
or a host differ.
Consider the example in the following figure, which shows two virtual machines running on a host. Each
block represents 4 KB of memory and each color/letter represents a different set of data on a block.
Figure 6‑2. Memory Usage Example
virtual machine
1
guest virtual memory
guest physical memory
machine memory
e
e
e
f
f
f
a
a
a
a
a
b
b
b
b
b
c
c
c c
c
d
d
d
virtual machine
2
The performance metrics for the virtual machines can be determined as follows:
n
To determine Memory Granted (the amount of guest physical memory that is mapped to machine
memory) for virtual machine 1, count the number of blocks in virtual machine 1's guest physical
memory that have arrows to machine memory and multiply by 4 KB. Since there are five blocks with
arrows, Memory Granted would be 20 KB.
n
Memory Consumed is the amount of machine memory allocated to the virtual machine, accounting for
savings from shared memory. First, count the number of blocks in machine memory that have arrows
from virtual machine 1's guest physical memory. There are three such blocks, but one block is shared
with virtual machine 2. So count two full blocks plus half of the third and multiply by 4 KB for a total of
10 KB Memory Consumed.
The important difference between these two metrics is that Memory Granted counts the number of blocks
with arrows at the guest physical memory level and Memory Consumed counts the number of blocks with
arrows at the machine memory level. The number of blocks differs between the two levels due to memory
sharing and so Memory Granted and Memory Consumed differ. This is not problematic and shows that
memory is being saved through sharing or other reclamation techniques.
vSphere Resource Management
44 VMware, Inc.