> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/knowledge-base/virtual-machines/resizing-a-virtual-disk-drive.md).

# Resizing a Virtual Disk Drive

Step-by-step instructions for increasing the size of a virtual disk drive in VergeOS, including notes on hot-plug support and guest OS requirements.

{% hint style="info" %}
**Note**

Drives can only be increased in size; they cannot be reduced. Verify whether your guest OS supports resizing without a power cycle, particularly for Virtio-SCSI drives.
{% endhint %}

To resize a virtual disk drive within a VM, follow these steps:

1. From the **VM Dashboard**, click **Drives** in the left menu.
2. Select the drive to be modified.
3. Click **Edit** in the left menu.
4. Modify the drive size as desired.
5. Click **Submit**.

## Important Notes

{% hint style="info" %}
**Note**

If the VM configuration allows hot-plugging, the disk interface is set to **Virtio-SCSI**, and the guest Operating System (OS) supports it, the drive size can typically be increased without power cycling the VM.
{% endhint %}

{% hint style="danger" %}
**Warning**

Drives cannot be reduced in size. While partitions may be resized inside the guest OS, the disk drive itself cannot be shrunk.
{% endhint %}

{% hint style="danger" %}
**Warning**

Modifications to drive size will most likely require corresponding changes within the guest Operating System to utilize the newly added space.
{% endhint %}

***

{% hint style="info" %}
**Document Information**

* Last Updated: 2024-08-29
* vergeOS Version: 4.12.6
  {% endhint %}


---

# 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://docs.verge.io/knowledge-base/virtual-machines/resizing-a-virtual-disk-drive.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.