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
n
Datastore Cluster B has an inter-VM anti-affinity rule. When you move a virtual disk out of Datastore
Cluster A and into Datastore Cluster B, any rule that applied to the virtual disk for a given virtual
machine in Datastore Cluster A no longer applies. The virtual disk is now subject to the inter-VM anti-
affinity rule in Datastore Cluster B.
n
Datastore Cluster B has an intra-VM anti-affinity rule. When you move a virtual disk out of Datastore
Cluster A and into Datastore Cluster B, the intra-VM anti-affinity rule does not apply to the virtual disk
for a given virtual machine because the rule is limited to only specified virtual disks in Datastore
Cluster B.
NOTE Storage DRS rules might prevent a datastore from entering maintenance mode. You can choose to
ignore Storage DRS rules for maintenance mode by enabling the Ignore Affinity Rules for Maintenance
option.
Create Inter-VM Anti-Affinity Rules
You can create an anti-affinity rule to indicate that all virtual disks of certain virtual machines must be kept
on different datastores. The rule applies to individual datastore clusters.
Virtual machines that participate in an inter-VM anti-affinity rule in a datastore cluster must be associated
with an intra-VM affinity rule in the datastore cluster. The virtual machines must also comply with the
intra-VM affinity rule.
If a virtual machine is subject to an inter-VM anti-affinity rule, the following behavior applies:
n
Storage DRS places the virtual machine's virtual disks according to the rule.
n
Storage DRS migrates the virtual disks using vMotion according to the rule, even if the migration is for
a mandatory reason such as putting a datastore in maintenance mode.
n
If the virtual machine's virtual disk violates the rule, Storage DRS makes migration recommendations to
correct the error or reports the violation as a fault if it cannot make a recommendation that will correct
the error.
No inter-VM anti-affinity rules are defined by default.
Procedure
1 Browse to the datastore cluster in the vSphere Web Client navigator.
2 Click the Manage tab and click Settings.
3 Under Configuration, select Rules.
4 Click Add.
5 Type a name for the rule.
6 From the Type menu, select VM anti-affinity.
7 Click Add.
8 Click Select Virtual Machine.
9 Select at least two virtual machines and click OK.
10 Click OK to save the rule.
vSphere Resource Management
102 VMware, Inc.