> 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-fails-with-error-unacceptable-cpu-info-cpu-doesn.md).

# Live Migration Fails With Error: "Unacceptable CPU Info: CPU Doesn't Have Compatibility.

## Problem

Attempts to perform a live migration of an instance fail with the following error.

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

```none
Unacceptable CPU info: CPU doesn't have compatibility.
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - v3.6.0 and Higher

## Cause

This error presents itself when CPU model/architecture differ between the source host and destination host even slightly.

## Resolution

1. Run the following command on the host where the VM currently resides to create an XML with the full CPU description.

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

```none
# virsh capabilities > virsh-caps-[originHostname]-full.xml
```

{% endtab %}
{% endtabs %}

2. Edit the XML file you've generated deleting everything above "\[cpu]" and everything below "\[/cpu]".
3. Move the file to the destination host and run the following command which will tell you if there is a legitimate mismatch and on which side it lies.

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

```none
# virsh cpu-compare virsh-caps-[originHostname]-full.xml
```

{% endtab %}
{% endtabs %}

4. To determine the specific features that must be masked out, run the following command.

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

```none
# virsh cpu-baseline virsh-caps-[originHostname]-full.xml
```

{% endtab %}
{% endtabs %}

5. Mask out the features that do not appear in the output of the command in Step #4 and attempt to migrate the VM again.


---

# 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/live-migration-fails-with-error-unacceptable-cpu-info-cpu-doesn.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.