> 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/how-to/vm-migration-failed-due-to-missing-libvirtd-s-socket-file-wip.md).

# VM Migration Failed Due To Missing Libvirtd's Socket File

## Problem

< A list of observable facts that characterize the undesirable behavior, starting with the most obvious and customer-identified, but continuing with those identified during the diagnostic process. Error messages, Bug references (link to Launchpad), log file entries, and behavior different than expected are all candidate symptoms. >

## Environment

* Platform9 Managed OpenStack - v4.0 and Higher

< The hardware, software, environmental conditions, and recent changes that are associated with this particular problem and resolution. Generally, our company’s product and/or product components are listed first. It’s OK for the environment to partially overlap with product category metadata. >

## Procedure

< A numbered series of steps to accomplish the objective. >

## Additional Information

< Links to supporting documentation, caveats, or other helpful background information that’s not strictly a problem, environment, cause, or resolution. >


---

# 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/how-to/vm-migration-failed-due-to-missing-libvirtd-s-socket-file-wip.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.