> 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/instances-enter-a-paused-state-on-the-hypervisor.md).

# Instances Enter a Paused State on the Hypervisor

## Problem

Instances running on a hypervisor go into a **paused** state. The following error is observed in the */var/log/pf9/ostackhost.log*.

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

```javascript
2021-08-31 09:40:12.849 ERROR nova.compute.manager [...] [instance: c67fc199-c897-4b42-8305-8a90f2473a23] Cannot reboot instance: Failed to read or write disk info file: [Errno 28] No space left on device: '/opt/pf9/data/instances/c67fc199-c897-4b42-8305-8a90f2473a23/disk.info.tmp': nova.exception.DiskInfoReadWriteFail: Failed to read or write disk info file: [Errno 28] No space left on device: '/opt/pf9/data/instances/c67fc199-c897-4b42-8305-8a90f2473a23/disk.info.tmp'
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - All Versions
* Nova

## Cause

The instances entered a **paused** state because there is no available disk space left on the *instances* mountpoint. When this happens, the instance state is reported as **ACTIVE** in the UI but the instances are in a **paused** state on the hypervisor.

## Resolution

1. Provision additional space to the *instances* mountpoint on the hypervisor.
2. Run the following commands for each instance present on the affected hypervisor to bring the instances back into a **running** state.

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

```javascript
# openstack server pause <server_uuid>
# openstack server unpause <server_uuid>
```

{% endtab %}
{% endtabs %}


---

# 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/instances-enter-a-paused-state-on-the-hypervisor.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.