> 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

Size the **host** and the **VEX-NX VM** separately. The OVA imports small on purpose; raise CPU, RAM, and disk before serious labs.

Supported hypervisors for the same OVA: **VMware Workstation 16+** and **ESXi / vSphere 6.7+ (7/8)**.

## Host (Workstation on Windows)

|          | Minimum                        | Recommended                   | Advanced          |
| -------- | ------------------------------ | ----------------------------- | ----------------- |
| Host RAM | 16 GB total (\~8 GB to the VM) | 32-48 GB (16-32 GB to the VM) | 64 GB+            |
| Host CPU | 4 cores with VT-x / AMD-V      | 8+ cores                      | 16+ cores         |
| Disk     | SSD, \~100 GB free             | NVMe, 250 GB+                 | NVMe, 500 GB-1 TB |
| Software | VMware Workstation 16+         | Same                          | Same              |

Leave headroom for Windows and Workstation. A 32 GB RAM lab VM usually wants a 48 GB+ physical machine.

## Host (ESXi)

|           | Minimum                                | Recommended                         | Advanced  |
| --------- | -------------------------------------- | ----------------------------------- | --------- |
| Host RAM  | Enough for VEX-NX + other VMs          | 64 GB+ on the host for serious labs | 128 GB+   |
| Host CPU  | VT-x/EPT or AMD-V; nested virt allowed | 8+ physical cores free for VEX-NX   | 16+ cores |
| Datastore | SSD/NVMe local preferred               | Same                                | Same      |
| Software  | ESXi / vSphere 6.7+ (7/8)              | Same                                | Same      |

## VEX-NX VM (appliance)

| Tier                           | vCPU   | RAM        | Hard Disk 1 | Typical use                                 |
| ------------------------------ | ------ | ---------- | ----------- | ------------------------------------------- |
| Absolute minimum (OVA default) | 4      | 8 GB       | 40+ GB SSD  | UI smoke test, a couple of light containers |
| Recommended                    | 8-16   | 16-32 GB   | 200-250 GB  | Mixed QEMU + Docker                         |
| Advanced                       | 16-32+ | 64-128+ GB | 500 GB-1 TB | Large EVPN / heavy appliances               |

* **Hard Disk 1** - OS, image library, overlays. Expand this as you grow.
* **Hard Disk 2** - install payload only; do not treat it as lab storage.

**Nested virtualization must be on:**

* Workstation: VM Settings -> Processors -> *Virtualize Intel VT-x/EPT or AMD-V/RVI*
* ESXi: *Expose hardware assisted virtualization to the guest*

After boot, open **Infrastructure** in the UI to confirm KVM, Docker, and usable CPU/RAM.

## Network adapters (OVA default)

| Adapter | OVF name   | Workstation      | ESXi (typical)       | Role                     |
| ------- | ---------- | ---------------- | -------------------- | ------------------------ |
| 1       | Management | VMnet0 Bridged   | Mgmt / VM Network    | Management / UI          |
| 2       | Internet   | VMnet8 NAT       | Uplink / internet PG | Lab NAT egress           |
| 3       | Lab        | VMnet1 Host-only | Isolated lab PG      | Bridge / host-only cloud |

Defaults for cloud templates are under **Infrastructure -> Cloud <-> VMware adapters**.


---

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