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

# Supported images

![Compatibility matrix](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2F0gmXqjf4H17w68Citwcu%2Fve20261112v5-images-compat.png?alt=media)

## Goal

Map common vendor folders to VEX-NX templates and know where to look next.

## How to use this page

1. Find your vendor / product
2. Note the **template ID** for Catalog / Import
3. Check live chips under [Catalog and Compatibility](/images/catalog-and-compatibility.md) for **Certified** vs Experimental
4. Import disks with Import images or [Bulk folder import](/images/bulk-folder-import.md)

VEX-NX never redistributes vendor images. Folder name examples are EVE-NG style hints only.

## Status source of truth

Do not treat any printed Certified list as permanent. After every appliance update, open **Images -> Compatibility** on **your** host.

**Certified** means honest verification: Start + live terminal + guest config (or documented N/A) + Stop/Wipe/Start retest. Templates that only boot Host OS or hang before the guest CLI stay **Experimental** until that bar passes.

## Common mappings (examples)

| Your folder hint                                   | Template ID                                          | Notes                                                 |
| -------------------------------------------------- | ---------------------------------------------------- | ----------------------------------------------------- |
| `iosv-*` / `vios-*`                                | `cisco-iosv`                                         | Nested KVM; HTML5 serial                              |
| `viosl2-*` / `iosvl2`                              | `iosvl2`                                             | L2 switch                                             |
| `csr1000v*`                                        | `csr1000v`                                           | Also SD-WAN CSR builds                                |
| `c8000v*`                                          | `catalyst-8000v`                                     | Prefer recommended CPU/RAM                            |
| `cat9kv-*` / `cat9000v*`                           | `cat9kv`                                             | Heavy guest                                           |
| `asav-*`                                           | `cisco-asav`                                         | SMBIOS quirks handled by runtime                      |
| `nxosv9k-*`                                        | `nxosv9000`                                          | UEFI/OVMF; recommend 4 vCPU / 12 GB                   |
| `iosxrv*` / `xrv9k*`                               | `xrv9k`                                              | Heavy; confirm Compatibility chip before class        |
| `veos-*`                                           | `arista-veos`                                        | Needs Aboot ISO + hda together                        |
| `fortinet-FGT-*`                                   | `fortigate`                                          |                                                       |
| `mikrotik-*`                                       | `mikrotik-chr`                                       | Light guest                                           |
| `vqfxre-*` / `vqfxpfe-*`                           | `vqfx`                                               | Pair RE + PFE                                         |
| `vmxvcp-*` / `vmxvfp-*`                            | `vmx`                                                | Pair VCP + VFP                                        |
| `vjunos*`                                          | `vjunos-switch` / `vjunos-router` / `vjunos-evolved` | Prefer bare metal; often Experimental until certified |
| `vtbond-*` / `vtedge-*` / `vtsmart-*` / `vtmgmt-*` | `vbond` / `vedge` / `vsmart` / `vmanage`             | SD-WAN set                                            |

## Multi-VM appliances

vQFX and vMX need two nodes (RE+PFE or VCP+VFP). Use **Add pair** when the catalog offers it, or add both nodes and interconnect.

## vJunos note

vJunos templates use a dedicated KVM launch profile. Prefer bare-metal USB. After first boot use Stop/Start, not Wipe, unless your notes say otherwise.

## Related

* [Catalog and Compatibility](/images/catalog-and-compatibility.md)
* [Library](/images/library.md)
* [Bulk folder import](/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 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/supported-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.