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
Prerequisites
Enable Storage DRS.
Procedure
1 Browse to the datastore cluster in the vSphere Client.
2 Click the Configure tab and click Services.
3 Under vSphere DRS click the Schedule DRS button.
4 In the Edit Datastore Cluster dialog box, click SDRS Scheduling.
5 Expand DRS Automation.
a Select an automation level.
b Set the Migration threshold.
Use the Migration slider to select the priority level of vCenter Server recommendations that adjust
the cluster's load balance.
c Select whether to enable Virtual Machine Automation.
Override for individual virtual machines can be set from the VM Overrides page.
6 Expand Power Managment.
a Select an automation level.
b Set the DPM threshold.
Use the DPM slider to select the power recommendations that vCenter Server will apply.
7 Type a Task name.
8 Type a description of the Task you have created.
9 Under Configured Scheduler, click Change and select the time for the task to run and click OK.
10 Type an email address to send a notification email to when the task is complete.
11 Click OK.
The scheduled task runs at the specified time.
Storage DRS Anti-Anity Rules
You can create Storage DRS anti-affinity rules to control which virtual disks should not be placed on the
same datastore within a datastore cluster. By default, a virtual machine's virtual disks are kept together on
the same datastore.
vSphere Resource Management
VMware, Inc. 113