> 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/pmk/frequently-asked-questions/du-vm-is-not-starting-up-due-to-memory-exhaustion-over-du-host.md).

# DU VM is not Starting up due to Memory Exhaustion Over DU Host

## Problem

* The DU VM is in shutoff state in the virsh list output.
* Libvirtd is complaining
* The workload cluster is running as expected.

## Environment

* Platform9 Edge Cloud

Cause

Due to not having enough free memory over the DU Host; the DU VM does not get provisioned. Libvirtd throws the below error in relevance to the memory scarcity.

{% tabs %}
{% tab title="Libvirtd logs" %}

```c
Jul  12 08:58:12 example.com libvirtd: 2024-07-08 04:03:24.312+0000: 1895: error : qemuMonitorOpenUnix:379 : failed to connect to monitor socket: No such process
Jul 12 08:59:22 example.com libvirtd: 2024-07-12 15:59:22.303+0000: 2206: error : virFork:332 : cannot fork child process: Cannot allocate memory
```

{% endtab %}
{% endtabs %}

## Resolution

* As per the default value for `vmMemoryMb`, DU VM requires minimum 8192Mi of memory (\~8 GB) to be provisioned and run over DU Host. The value vmMemoryMb can be fetched from airctl-config.yaml file in DU Host


---

# 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/pmk/frequently-asked-questions/du-vm-is-not-starting-up-due-to-memory-exhaustion-over-du-host.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.