> 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/libvirt-randomly-crashes-on-ubuntu-16-04-xenial-with-error-erro.md).

# Libvirt Randomly Crashes on Ubuntu 16.04, "Error in \`/usr/sbin/libvirtd': malloc(): memory corruption:"

## Problem

**Libvirt** is intermittently/randomly crashing with an error related to memory corruption: ``Error in `/usr/sbin/libvirtd': malloc(): memory corruption:``

## Environment

* Platform9 Managed OpenStack - All Version
* Libvirt

## Cause

The root-cause has yet to be determined. Our team will update this document as soon as any new information becomes available.

## Resolution

No particular resolution exists for this issue at the moment. In general, ensure that your system isn't contended on memory and avoid setting too high of a memory overcommit.

## Additional Information

[LP#1643911 – libvirt randomly crashes on xenial nodes with "\*\*\* Error in \`/usr/sbin/libvirtd': malloc(): memory corruption:"](https://bugs.launchpad.net/nova/+bug/1643911)


---

# 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/libvirt-randomly-crashes-on-ubuntu-16-04-xenial-with-error-erro.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.