6.5.1

Virtual Machine is Pinned
This fault occurs when DRS cannot move a virtual machine because DRS is disabled on it. That is, the virtual
machine is "pinned" on its registered host.
Virtual Machine not Compatible with any Host
This fault occurs when DRS cannot nd a host that can run the virtual machine.
This might occur, for example, if no host can satisfy the virtual machine's CPU or memory resource needs or
if no host currently has network or storage access needed by the virtual machine.
To address this problem, provide a host that can meet the virtual machine's requirements.
VM/VM DRS Rule Violated when Moving to another Host
This fault occurs when more than one virtual machines running on the same host and share anity rules
with each other cannot be moved to another host.
This might occur because not all the virtual machines can vMotion o the current host. For example, one of
the virtual machines in the group is DRS-disabled.
To prevent this, check for reasons why some virtual machines in the group cannot vMotion.
Host Incompatible with Virtual Machine
This fault occurs when DRS considers migrating a virtual machine to a host, but nds that the host is
incompatible with the given virtual machine.
This might occur because the target host does not have access to the network or storage connection needed
by the virtual machine. Another reason this fault occurs is if the target host has a CPU that diers
suciently from the current host so that using vMotion amongst the hosts is not supported.
To avoid this, create clusters such that all hosts are congured consistently and vMotion is compatible
amongst the hosts.
Another reason the host is incompatible with the virtual machine is that there is a required VM/Host DRS
rule in place that instructs DRS to never place this virtual machine on this host.
Host Has Virtual Machine That Violates VM/VM DRS Rules
This fault occurs when the virtual machine, when powered on or moved by starting vMotion, might violate
a VM/VM DRS rule.
The virtual machine can still be manually powered on or moved with vMotion, but vCenter Server cannot
automatically do so.
Host has Insufficient Capacity for Virtual Machine
This fault occurs when the host does not have enough CPU or memory capacity for running the virtual
machine.
Host in Incorrect State
This fault occurs when the host is entering maintenance or standby state when needed for DRS action to
occur.
To address this fault, cancel the request for the host to enter standby or maintenance mode.
vSphere Resource Management
124 VMware, Inc.