> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/solution/live-migration-of-instance-with-config-drive-fails.md).

# Live-Migration of Instance With Config Drive Fails

## Problem

* An instance which has **config\_drive** set to **True** fails to live-migrate.
* The destination hypervisor reports the following error in */var/log/pf9/ostackhost.log.*

{% tabs %}
{% tab title="None" %}

```none
ERROR oslo_messaging.rpc.server [...] Exception during message handling: InvalidSharedStorage: 0f15c8ad-bbeb-473b-9aa9-3bf38cc952d5 is not on shared storage: Shared storage live-migration requires either shared storage or boot-from-volume with no local disks.
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - v3.6 - v3.11
* Nova
* Libvirt

## Cause

Due to a limitation with the corresponding Libvirt version, a configuration drive using the ISO-9660 format cannot be live-migrated.

## Resolution

To migrate the instance, you will need to perform a cold (non-live) migration, or snapshot and re-create it.

### Workaround

As per the guidance outlined in the [configuration drive format](https://docs.openstack.org/newton/user-guide/cli-config-drive.html#configuration-drive-format), you may be successful in leveraging the legacy VFAT format for future instances which require to be live-migrated with a config-drive attached.

## Additional Information

* [OpenStack Docs: Configure live migrations](https://docs.openstack.org/nova/pike/admin/configuring-migrations.html)
* [OpenStack Docs: Config Drive](https://docs.openstack.org/nova/queens/user/config-drive.html)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmo/solution/live-migration-of-instance-with-config-drive-fails.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 `build a script that syncs our docs to a CMS` 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.