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
You can remove a virtual machine from a cluster in two ways.
n
When you remove a host from a cluster, all of the powered-off virtual machines that you do not
migrate to other hosts are removed as well. You can remove a host only if it is in maintenance mode
or disconnected. If you remove a host from a DRS cluster, the cluster can become yellow because it
is overcommitted.
n
You can migrate a virtual machine from a cluster to a standalone host or from a cluster to another
cluster using the Migrate wizard. To start this wizard right-click the virtual machine name and select
Migrate.
Move a Virtual Machine Out of a Cluster
You can move a virtual machine out of a cluster.
Procedure
1 Browse to the virtual machine in the vSphere Client.
a To find a virtual machine, select a data center, folder, cluster, resource pool, or host.
b Click the VMs tab.
2 Right-click the virtual machine and select Migrate.
3 Select Change datastore and click Next.
4 Select a datastore and click Next.
5 Click Finish.
If the virtual machine is a member of a DRS cluster rules group, vCenter Server displays a warning
before it allows the migration to proceed. The warning indicates that dependent virtual machines are
not migrated automatically. You have to acknowledge the warning before migration can proceed.
Removing a Host from a Cluster
When you remove a host from a DRS cluster, you affect resource pool hierarchies, virtual machines, and
you might create invalid clusters. Consider the affected objects before you remove the host.
n
Resource Pool Hierarchies – When you remove a host from a cluster, the host retains only the root
resource pool, even if you used a DRS cluster and decided to graft the host resource pool when you
added the host to the cluster. In that case, the hierarchy remains with the cluster. You can create a
host-specific resource pool hierarchy.
Note Ensure that you remove the host from the cluster by first placing it in maintenance mode. If you
instead disconnect the host before removing it from the cluster, the host retains the resource pool that
reflects the cluster hierarchy.
vSphere Resource Management
VMware, Inc. 84