> 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/images/import-images.md).

# Import images

![Import and Prepare](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2Fb9bZUV2GylAPOdViaVJZ%2Fve20261112v5-images-import.png?alt=media)

## Goal

Add a vendor disk to the Library and bind it to a template so QEMU nodes can Start.

## Why Import exists

Catalog templates are blueprints. Without a disk file in Library, commercial appliances have nothing to boot. Import is how your licensed files become usable on this appliance.

## Three paths on Images -> Import

| Path                  | Why use it                                                  | Example                                   |
| --------------------- | ----------------------------------------------------------- | ----------------------------------------- |
| **Convert & add**     | OVA / VMDK / qcow2 / ISO with progress                      | Drop a vendor OVA, pick template, convert |
| **Upload ready disk** | Already `hda.qcow2` / virtio - no convert                   | Fast path if you prepared elsewhere       |
| **Bulk import**       | SCP many folders to staging, scan, import/convert what fits | Lab full of appliance folders             |

## Recipe: Convert & add (GUI upload)

1. Images -> **Import**
2. Use **Convert & add**
3. Upload the disk (keep the browser tab open for large files)
4. Choose the matching **template**
5. Confirm conversion / copy into Library
6. Start a node and select the new disk when asked

## Recipe: Upload ready disk

1. Images -> **Import** -> **Upload ready disk**
2. Select the template (required so files map to the right product)
3. Choose `hda.qcow2` / `virtioa.qcow2` (and extras the form asks for)
4. **Upload**

Arista vEOS needs **cdrom.iso** (Aboot) as well as `hda.qcow2` - pick both, or use Convert & add / Bulk.

## Recipe: Bulk / folder import

1. Stage files under the appliance staging path (SSH as **vexnx**), or follow [Bulk folder import](/images/bulk-folder-import.md)
2. Scan -> confirm template match
3. Confirm import into Library (or Convert selected when prepare is needed)

## Expected result

* Disk appears in Library under the template
* Compatibility still shows the template status (Certified / Verified / Experimental) - importing a disk does not change that chip

## If it fails

| Symptom                      | Fix                                                                         |
| ---------------------------- | --------------------------------------------------------------------------- |
| Bad Gateway / timeout        | Free disk; smaller chunks; stay on the page                                 |
| Permission denied on staging | SSH as **vexnx**; staging dirs mode 0777; restart API if needed             |
| Wrong template               | Re-import with correct ID ([Supported images](/images/supported-images.md)) |
| Disk full during convert     | Free Library space or grow the appliance disk                               |

## Related

* [Bulk folder import](/images/bulk-folder-import.md)
* [Catalog and Compatibility](/images/catalog-and-compatibility.md)
* [Library](/images/library.md)
* [Migrate Lab](/labs/migrate-lab.md) (topology ZIP still needs disks here)


---

# 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.vex-nx.com/images/import-images.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.