6.5.1
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
- 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
- Index
Create a VM-VM Affinity Rule
You can create VM-VM anity rules to specify whether selected individual virtual machines should run on
the same host or be kept on separate hosts.
N If you use the vSphere HA Specify Failover Hosts admission control policy and designate multiple
failover hosts, VM-VM anity rules are not supported.
Procedure
1 Browse to the cluster in the vSphere Web Client navigator.
2 Click the tab.
3 Under , click VM/Host Rules.
4 Click Add.
5 In the Create VM/Host Rule dialog box, type a name for the rule.
6 From the Type drop-down menu, select either Keep Virtual Machines Together or Separate Virtual
Machines.
7 Click Add.
8 Select at least two virtual machines to which the rule will apply and click OK.
9 Click OK.
VM-VM Affinity Rule Conflicts
You can create and use multiple VM-VM anity rules, however, this might lead to situations where the
rules conict with one another.
If two VM-VM anity rules are in conict, you cannot enable both. For example, if one rule keeps two
virtual machines together and another rule keeps the same two virtual machines apart, you cannot enable
both rules. Select one of the rules to apply and disable or remove the conicting rule.
When two VM-VM anity rules conict, the older one takes precedence and the newer rule is disabled. DRS
only tries to satisfy enabled rules and disabled rules are ignored. DRS gives higher precedence to preventing
violations of anti-anity rules than violations of anity rules.
VM-Host Affinity Rules
A VM-Host anity rule species whether or not the members of a selected virtual machine DRS group can
run on the members of a specic host DRS group.
Unlike a VM-VM anity rule, which species anity (or anti-anity) between individual virtual machines,
a VM-Host anity rule species an anity relationship between a group of virtual machines and a group of
hosts. There are 'required' rules (designated by "must") and 'preferential' rules (designated by "should".)
A VM-Host anity rule includes the following components.
n
One virtual machine DRS group.
n
One host DRS group.
n
A designation of whether the rule is a requirement ("must") or a preference ("should") and whether it is
anity ("run on") or anti-anity ("not run on").
Because VM-Host anity rules are cluster-based, the virtual machines and hosts that are included in a rule
must all reside in the same cluster. If a virtual machine is removed from the cluster, it loses its DRS group
aliation, even if it is later returned to the cluster.
vSphere Resource Management
88 VMware, Inc.