VMCP might not be able to find a compatible host for a virtual machine if its swapfile is on a local datastore.


If a virtual machine has its swapfile configured to be on a host-local datastore rather than in the default directory where the VM's configuration file resides, VMCP might not restart the VM on a healthy host if it is affected by an All Paths Down (APD) datastore accessibility failure.


VMCP monitors the list of datastores that a virtual machine depends on, including the datastores where the VM's configuration file, swapfile and disks reside. When an APD failure is detected on a dependent datastore, VMCP first determines if there is another host which is compatible and has sufficient capacity to failover the affected VM to. To determine this compatibility, VMCP considers the dependent datastores along with other factors such as CPU and memory reservations. If a suitable host is found, VMCP terminates the VM on the host that experienced the APD failure.

However, if a VM's swapfile is on a host-local datastore, such a datastore might not be configured on other hosts in the cluster. This situation prevents VMCP from finding a compatible host to fail over the VM, and the VM continues running on the host which experienced an APD failure.


  • Keep the VM swap file in the default directory, or ensure that the host-local datastore that the VM's swapfile resides on is shared among a set of hosts.