> For the complete documentation index, see [llms.txt](https://docs.vex-nx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vex-nx.com/vex-nx-user-guide-1/images/library.md).

# Library

**Images -> Library** lists registered disks.

## What you can do

1. Search by label, platform hint, vendor, checksum.
2. Click a row to open the inspector.
3. Set **Platform / template** mapping and optional **Version**, then save.
4. **Validate** a disk (smoke checks on this appliance).
5. **Quarantine** a bad disk so Validate flags labs that still reference it.
6. **Grow disk** for qcow2 images when you need more capacity (prompt asks for size in GB).
7. **Delete** when you are sure nothing needs the file.

## States you will see

| State                | Meaning                                                      |
| -------------------- | ------------------------------------------------------------ |
| Registered / pending | In the library; may still need validation                    |
| Verified             | Passed checks on this platform                               |
| Quarantined          | Failed or manually quarantined - fix or replace before class |

Files live under `/opt/pram/images/` (and runtime subfolders) on the guest.

When a QEMU node starts, it must point at a Library entry that matches the template you placed on the canvas.

To add disks, use **Images -> Import** (Convert & add, ready upload, or [Bulk](/vex-nx-user-guide-1/images/bulk-folder-import.md)).


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vex-nx.com/vex-nx-user-guide-1/images/library.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.