DRS faults indicate the reasons that prevent the generation of DRS actions (or the recommendation of those actions in manual mode). The DRS faults are defined within this section. Virtual Machine is PinnedThis 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 HostThis fault occurs when DRS cannot find a host that can run the virtual machine. VM/VM DRS Rule Violated when Moving to another HostThis fault occurs when more than one virtual machines running on the same host and share affinity rules with each other cannot be moved to another host. Host Incompatible with Virtual MachineThis fault occurs when DRS considers migrating a virtual machine to a host, but finds that the host is incompatible with the given virtual machine. Host has Virtual Machine that Violates VM/VM DRS RulesThis fault occurs when the virtual machine, when powered on or moved by starting vMotion, would violate a VM/VM DRS rule. Host has Insufficient Capacity for Virtual MachineThis fault occurs when the host does not have enough CPU or memory capacity for running the virtual machine. Host in Incorrect StateThis fault occurs when the host is entering maintenance or standby state when needed for DRS action to occur. Host has Insufficient Number of Physical CPUs for Virtual MachineThis fault occurs when the host hardware does not enough physical CPUs (hyperthreads) to support the number of virtual CPUs in the virtual machine. Host has Insufficient Capacity for Each Virtual Machine CPUThis fault occurs when the host does not have enough CPU capacity for running the virtual machine. The Virtual Machine is in vMotionThis fault occurs when DRS cannot move a virtual machine because it is in vMotion. No Active Host in ClusterThis fault occurs when the cluster in which the virtual machine is being moved does not contain any hosts that are connected and in a non-maintenance state. Insufficient ResourcesThis fault occurs when an attempted operation conflicts with a resource configuration policy. Insufficient Resources to Satisfy Configured Failover Level for HAThis fault occurs when the HA configuration of CPU or memory resources reserved for failover is violated or cannot be met by the DRS operation under consideration. No Compatible Hard Affinity HostNo host is available for the virtual machine that satisfies its mandatory VM/Host DRS affinity or anti-affinity rules. No Compatible Soft Affinity HostNo host is available for the virtual machine that satisfied its preferred VM/Host DRS affinity or anti-affinity rules. Soft Rule Violation Correction DisallowedDRS migration threshold is set at mandatory-only. Soft Rule Violation Correction ImpactCorrecting the non-mandatory VM/Host DRS affinity rule does not occur because it impacts performance.