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
Managing Storage I/O Resources 8
vSphere Storage I/O Control allows cluster-wide storage I/O prioritization, which allows better workload
consolidation and helps reduce extra costs associated with over provisioning.
Storage I/O Control extends the constructs of shares and limits to handle storage I/O resources. You can
control the amount of storage I/O that is allocated to virtual machines during periods of I/O congestion,
which ensures that more important virtual machines get preference over less important virtual machines for
I/O resource allocation.
When you enable Storage I/O Control on a datastore, ESXi begins to monitor the device latency that hosts
observe when communicating with that datastore. When device latency exceeds a threshold, the datastore is
considered to be congested and each virtual machine that accesses that datastore is allocated I/O resources
in proportion to their shares. You set shares per virtual machine. You can adjust the number for each based
on need.
Configuring Storage I/O Control is a two-step process:
1 Enable Storage I/O Control for the datastore.
2 Set the number of storage I/O shares and upper limit of I/O operations per second (IOPS) allowed for
each virtual machine.
By default, all virtual machine shares are set to Normal (1000) with unlimited IOPS.
NOTE Storage I/O Control is enabled by default on Storage DRS-enabled datastore clusters.
This chapter includes the following topics:
n
“Storage I/O Control Requirements,” on page 49
n
“Storage I/O Control Resource Shares and Limits,” on page 50
n
“Set Storage I/O Control Resource Shares and Limits,” on page 51
n
“Enable Storage I/O Control,” on page 51
n
“Set Storage I/O Control Threshold Value,” on page 52
n
“Storage DRS Integration with Storage Profiles,” on page 53
Storage I/O Control Requirements
Storage I/O Control has several requirements and limitations.
n
Datastores that are Storage I/O Control-enabled must be managed by a single vCenter Server system.
n
Storage I/O Control is supported on Fibre Channel-connected, iSCSI-connected, and NFS-connected
storage. Raw Device Mapping (RDM) is not supported.
VMware, Inc.
49