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‑3. Advanced Virtual Machine Attributes (Continued)
Attribute Description Default
sched.mem.pshare.salt A salt value is a configurable VMX option for each virtual
machine. If this option is not present in the virtual
machine's VMX file, then the value of vc.uuid vmx
option is taken as the default value. Since the vc.uuid is
unique to each virtual machine, by default transparent
page sharing happens only among the pages belonging to
a particular virtual machine (intra-VM). If a group of virtual
machines are considered trustworthy, it is possible to
share pages among them by setting a common salt value
for all of those virtual machines (inter-VM).
user configurable
sched.swap.persist Specifies whether the virtual machine’s swap files should
persist or be deleted when the virtual machine is powered
off. By default, the system creates the swap file for a
virtual machine when the virtual machine is powered on,
and deletes the swap file when the virtual machine is
powered off.
False
sched.swap.dir Directory location of the virtual machine's swap file.
Defaults to the virtual machine's working directory, that is,
the directory that contains its configuration file. This
directory must remain on a host that is accessible to the
virtual machine. If you move the virtual machine (or any
clones created from it), you might need to reset this
attribute.
Equals workingDir
Advanced Virtual NUMA Attributes
You can use the advanced virtual NUMA attributes to customize virtual NUMA usage.
Table 16‑4. Advanced NUMA Attributes
Attribute Description Default
cpuid.coresPerSocket Determines the number of virtual cores per virtual CPU socket.
If the value is greater than 1, also determines the size of virtual
NUMA nodes if a virtual machine has a virtual NUMA topology.
You can set this option if you know the exact virtual NUMA
topology for each physical host.
1
numa.autosize When you set this option, the virtual NUMA topology has the
same number of virtual CPUs per virtual node as there are
cores on each physical node.
FALSE
numa.autosize.once When you create a virtual machine template with these settings,
the settings are guaranteed to remain the same every time you
subsequently power on the virtual machine. The virtual NUMA
topology will be reevaluated if the configured number of virtual
CPUs on the virtual machine is modified.
TRUE
numa.vcpu.maxPerVirtualNode If cpuid.coresPerSocket is too restrictive as a power of two,
you can set numa.vcpu.maxPerVirtualNode directly. In this
case, do not set cpuid.coresPerSocket.
8
vSphere Resource Management
VMware, Inc. 132