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
Advanced Memory Attributes
You can use the advanced memory attributes to customize memory resource usage.
Table 15‑1. Advanced Memory Attributes
Attribute Description Default
Mem.ShareForceSalting Mem.ShareForceSalting 0: Inter-virtual machine Transparent Page
Sharing (TPS) behavior is still retained. The value of VMX option
sched.mem.pshare.salt is ignored even if present.
Mem.ShareForceSalting 1: By default the salt value is taken from
sched.mem.pshare.salt. If not specified, it falls back to old TPS
(inter-VM) behavior by considering salt values for the virtual
machine as 0.
Mem.ShareForceSalting 2: By default the salt value is taken from
sched.mem.pshare.salt if present, or vc.uuid. If it does not
exist, then the page sharing algorithm generates random and
unique value for salting per virtual machine, which is not
configurable by users.
2
Mem.SamplePeriod Specifies the periodic time interval, measured in seconds of the
virtual machine’s execution time, over which memory activity is
monitored to estimate working set sizes.
60
Mem.BalancePeriod Specifies the periodic time interval, in seconds, for automatic
memory reallocations. Significant changes in the amount of free
memory also trigger reallocations.
15
Mem.IdleTax Specifies the idle memory tax rate, as a percentage. This tax
effectively charges virtual machines more for idle memory than for
memory they are actively using. A tax rate of 0 percent defines an
allocation policy that ignores working sets and allocates memory
strictly based on shares. A high tax rate results in an allocation
policy that allows idle memory to be reallocated away from virtual
machines that are unproductively hoarding it.
75
Mem.ShareScanGHz Specifies the maximum amount of memory pages to scan (per
second) for page sharing opportunities for each GHz of available
host CPU resource. For example, defaults to 4 MB/sec per 1 GHz.
4
Mem.ShareScanTime Specifies the time, in minutes, within which an entire virtual
machine is scanned for page sharing opportunities. Defaults to 60
minutes.
60
Mem.CtlMaxPercent Limits the maximum amount of memory reclaimed from any
virtual machine using the memory balloon driver (vmmemctl),
based on a percentage of its configured memory size. Specify 0 to
disable reclamation for all virtual machines.
65
Mem.AllocGuestLargePage Enables backing of guest large pages with host large pages.
Reduces TLB misses and improves performance in server
workloads that use guest large pages. 0=disable.
1
Mem.AllocUsePSharePool
and
Mem.AllocUseGuestPool
Reduces memory fragmentation by improving the probability of
backing guest large pages with host large pages. If host memory is
fragmented, the availability of host large pages is reduced. 0 =
disable.
15
Mem.MemZipEnable Enables memory compression for the host. 0 = disable. 1
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
vSphere Resource Management
116 VMware, Inc.