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
Table 15‑3. Advanced Virtual Machine Attributes (Continued)
Attribute Description Default
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 15‑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
numa.vcpu.min Minimum number of virtual CPUs in a virtual machine
that are required in order to generate a virtual NUMA
topology.
9
numa.vcpu.maxPerMachineNode Maximum number of virtual CPUs that belong to the same
virtual machine that can be scheduled on a NUMA node
at the same time. Use this attribute to ensure maximum
bandwidth, by forcing different NUMA clients on
different NUMA nodes.
Number of
cores per
node on the
physical host
where a
virtual
machine is
running.
numa.vcpu.maxPerClient Maximum number of virtual CPUs in a NUMA client. A
client is a group of virtual CPUs that are NUMA-managed
as a single entity. By default, each virtual NUMA node is a
NUMA client, but if a virtual NUMA node is larger than a
physical NUMA node, a single virtual NUMA node can be
backed by multiple NUMA clients.
Equals
numa.vcpu.m
axPerMachin
eNode
Chapter 15 Advanced Attributes
VMware, Inc. 119