> 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.10/storage/storage-live-migration.md).

# Storage Live Migration

Storage live migration is a capability that ensures that a virtual machine's underlying storage is migrated when you invoke live migration for that VM.

<code class="expression">space.vars.product\_name</code> fully supports storage live migration. This includes the following scenarios:

1. **Live migration of ephemeral / local storage for virtual machines -** When you live migration a VM that is booted from an image and is using host local storage, <code class="expression">space.vars.product\_name</code> will behind the scenes migrate storage for that VM to the destination host's local storage.
2. **Live migration of block storage** - You can also live migrate virtual machines that are using block storage, both VMs booted from block storage as well as VMs booted from an image but using block storage in addition. Read [Block Storage Live Migration / Retyping](/private-cloud-director/2025.10/storage/volume.md#volume-retype-changing-volume-type-and-migration-across-backends) for more details.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform9.com/private-cloud-director/2025.10/storage/storage-live-migration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.