> 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/can-i-live-migrate-an-instance-across-availability-zones.md).

# Can I Live Migrate an Instance Across Availability Zones?

## Problem

* Live migration of instance across availability zone is failing
* Below messages are reported in logs

*/var/log/nova/nova-conductor.log*

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

```none
WARNING nova.scheduler.utils [...] Failed to compute_task_migrate_server: No valid host was found
```

{% endtab %}
{% endtabs %}

*/var/log/nova/nova-scheduler.log*

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

```none
INFO nova.scheduler.host_manager [...] Host filter only checking host [...] and node [hostname]INFO nova.filters [...] Filter AvailabilityZoneFilter returned 0 hosts
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - All versions
* Nova

## Cause

Live migration of instance is possible across the availability zone but only using CLI. As we can see both the source and destination host are part of different availability zones.

* * Source Host

```
$ openstack compute service list | grep [UUID]| 50 | nova-compute    | [UUID] | Test-AZ | enabled  | up    | 2020-XX-XXTYY:YY:YY.000000 |
```

```
- Destination Host
```

```
$ openstack compute service list | grep [UUID]| 69 | nova-compute    | [UUID] | nova       | enabled  | up    | 2020-XX-XXTYY:YY:YY.000000 |
```

## Resolution

* Live migration between different availability zones works with the **--force** parameter to live-migration. Migrating instances using **--force** option, can forcefully bypass the ***nova-scheduler*** and move an instance to a specified host.

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

```none
$ nova live-migration [--block-migrate] [--force] [server] [[host]]
```

{% endtab %}
{% endtabs %}

## Additional Information

Refer the OpenStack documentation for more details on the [Availability Zones.](https://docs.openstack.org/nova/latest/admin/availability-zones.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 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/can-i-live-migrate-an-instance-across-availability-zones.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.