> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/private-cloud-director/2025.6/virtualized-clusters/virtualized-cluster/virtual-machine-high-availability-vm-ha.md).

# Virtual Machine High Availability (VM HA)

Virtual Machine High Availability (VM HA) is a core <code class="expression">space.vars.product\_name</code> capability that automatically detects physical host failures within a virtualized cluster and restarts the affected VMs on other healthy hosts in the same cluster.

<code class="expression">space.vars.product\_name</code> VM HA delivers a safety net for production workloads being deployed on a virtualized clusters. By turning on VM HA for your cluster, you can ensure that the VMs running on this cluster will remain operating across host failures.

## Pre-requisites

Following are VM HA pre-requisites:

* VM HA always operates in the context of a virtualized cluster. You need to turn it on as a cluster level property. Once turned on, VM HA applies to all virtual machines within the cluster.
* Shared storage is a required for VM HA. For VM HA to work at the cluster level:
  * All VMs should be using block storage volume as root disk (non ephemeral root disk), or
  * If any VMs are using ephemeral storage for root disk, then [Ephemeral Shared Storage](/private-cloud-director/2025.6/storage/storage-overview1sq.md#ephemeral-shared-storage) should be used for all hosts in the virtualized cluster.
  * When [Ephemeral Shared Storage](/private-cloud-director/2025.6/storage/storage-overview1sq.md#ephemeral-shared-storage) is not used, any VMs using ephemeral root disk will get [rebuilt](/private-cloud-director/2025.6/virtualized-clusters/deploying-workloads.md#rebuild-vm) as part of recovery on another host.
* VM HA requires a **minimum number of healthy hosts** in a cluster to function correctly. **A minimum of two hosts** is required for HA activation.
* VM HA uses [VM Evacuation](/private-cloud-director/2025.6/virtualized-clusters/deploying-workloads/vm-migration.md#vm-evacuation) operation behind the scenes. [VM Evacuation Prerequisites](/private-cloud-director/2025.6/virtualized-clusters/deploying-workloads/vm-migration.md#prerequisites) must be met for the operation to succeed.

## How VM HA Works

The process is designed to be automatic and requires minimal manual intervention during a failure event:

* **Continuous Host Monitoring:** VM HA service constantly monitors the health and responsiveness of all hypervisor hosts participating in an HA-enabled virtualized cluster.
* **Failure Detection:** If a host stops responding (due to hardware failure, operating system crash, or certain network isolation scenarios), the system detects the failure
* **Automatic VM Recovery:** Once a host failure is confirmed, which involves both the management plane and cluster hosts to confirm failure, VM HA automatically initiates the process of restarting any VMs that were running on the failed host. These VMs are powered on using available resources on the remaining healthy hosts within the cluster.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.platform9.com/private-cloud-director/2025.6/virtualized-clusters/virtualized-cluster/virtual-machine-high-availability-vm-ha.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.