> 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/frequently-asked-questions/live-migration-failure-with-error---the-instance-requires-a-newe.md).

# Live Migration Failure With Error: "The instance requires a newer hypervisor version than has been provided."

## Problem

Live Migration Failure With Error: "The instance requires a newer hypervisor version than has been provided."

{% tabs %}
{% tab title="Nova Conductor Debug logs" %}

```javascript
2024-10-02 19:51:45.109 7549 DEBUG nova.conductor.tasks.live_migrate [req-bfd4fa06-9205-443e-b80e-0b0062ae8d3b aa3ada4a824f4f87be8d23a8138b9751 0b81ca966e6447829b8c0181c237d96d - default default] Skipping host: 7faf9b59-9ad9-4916-8332-15fb703459b8 because: The instance requires a newer hypervisor version than has been provided. _find_destination /opt/pf9/nova/lib/python3.9/site-packages/nova/conductor/tasks/live_migrate.py:560
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - All versions

## Answer

* This is an expected behaviour with Nova. By default, a live migration from higher libvirt/qemu versions to lower versions is not supported.
* Nova has the following codes to check hypervisor compatibility.

```javascript
---- conductor/tasks/live_migrate.py ----
def _check_compatible_with_source_hypervisor(self, destination):
source_info = self._get_compute_info(self.source)
destination_info = self._get_compute_info(destination)

source_type = source_info['hypervisor_type']
destination_type = destination_info['hypervisor_type']
if source_type != destination_type:
raise exception.InvalidHypervisorType()

source_version = source_info['hypervisor_version']
destination_version = destination_info['hypervisor_version']
if source_version > destination_version:
raise exception.DestinationHypervisorTooOld()
```

## Additional Information

Refer to a similar issue reported by RedHat: <https://access.redhat.com/solutions/3587091>


---

# 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/frequently-asked-questions/live-migration-failure-with-error---the-instance-requires-a-newe.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.