> 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/instance-fails-to-live-migrate-no-valid-host-was-found.md).

# Instance Fails to Live-Migrate: "No valid host was found

## Problem

* An instance is failing to live-migrate with "No valid host was found".
* The instance is associated with an Availability Zone.
* The live-migration is shown to be in error as per **`nova server-migration-show`**.
* In */var/log/nova/nova-scheduler.log* on the Management Plane, the following is observed.

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

```none
INFO nova.filters [...] Filtering removed all hosts for the request with instance ID '[INSTANCE_UUID]'. Filter results: ['RetryFilter: (start: 1, end: 1)', 'AggregateMultiTenancyIsolation: (start: 1, end: 1)', 'AvailabilityZoneFilter: (start: 1, end: 0)']
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - v3.11 and Lower
* Nova

## Cause

The instance is being attempted to be live-migrated across Availability Zones, which is not allowed.

## Resolution

### Adding Additional Hosts

1. In Clarity UI, navigate to "Infrastructure" → "Host Aggregates".
2. Select the radio button next to the name of the host aggregate associated with the AZ for which the instance is provisioned under.
3. Click "Edit Host Aggregate".
4. Select the checkbox next to each additional host to be added to the aggregate.
5. Click "Save".
6. The host should now show for the AZ under the Availability Zones tab.
7. Retry the live-migration.

## Additional Information

* [Platform9 Docs - Host Aggregates](https://docs.platform9.com/openstack/infrastructure/host-aggregates/)


---

# 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/instance-fails-to-live-migrate-no-valid-host-was-found.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.