> 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/getting-started/system-requirements.md).

# System requirements

![System and host capacity](https://1807546539-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhgHCHWL3861o2DBW53aA%2Fuploads%2FDuh5rzclbBuDf9rd95hE%2Fve20261112v5-infrastructure.png?alt=media)

## Goal

Size the host so first boot and first labs succeed.

## Absolute minimum (OVA default)

| Resource            | Minimum                              |
| ------------------- | ------------------------------------ |
| vCPU                | 4                                    |
| RAM                 | 8 GB                                 |
| Disk 1 (OS + app)   | 40+ GB SSD                           |
| Nested VT-x / AMD-V | Required for QEMU labs inside VMware |

Raise resources **before** you start many QEMU nodes or vJunos.

## Recommended

| Tier                  | vCPU   | RAM        | Disk                |
| --------------------- | ------ | ---------- | ------------------- |
| Teaching / light      | 8-16   | 16-32 GB   | 200-250 GB SSD/NVMe |
| Advanced / nested NOS | 16-32+ | 64-128+ GB | 500 GB-1 TB NVMe    |

## Nested virtualization (VMware)

On the Windows host: Hyper-V / `hypervisorlaunchtype` must be **Off** so Workstation can expose VT-x.

On the VEX-NX VM settings:

1. **Virtualize Intel VT-x/EPT or AMD-V/RVI** - on
2. **Virtualize CPU performance counters** - on
3. Virtualize IOMMU - optional

Inside the guest after boot:

```bash
ls -l /dev/kvm
```

If `/dev/kvm` is missing, QEMU Start fails for KVM-required templates.

## Bare metal

Prefer Install from USB for deep nested guests (vJunos, nested ESXi labs). Enable VT-x / AMD-V in BIOS/UEFI.

## Browser

Current Chrome, Edge, or Firefox. Allow pop-ups if you use external SecureCRT/PuTTY helper links.

## Next

* Install the OVA
* Install from USB (bare metal)
* Sizing and upgrades


---

# 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/getting-started/system-requirements.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.