> 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/getting-started/install-the-ova.md).

# Install the OVA

One `vex-nx-<version>.ova` works on **VMware Workstation 16+** and **ESXi / vSphere 6.7+ (7/8)**.

* Workstation detail: Workstation import (in the docs tree) / steps below
* ESXi detail: ESXi import

## Before you start

1. Confirm VT-x / AMD-V is enabled in BIOS/UEFI (and nested virt will be exposed to the guest).
2. Have enough free disk for the OVA plus expanded Hard Disk 1.
3. Note the OVA filename (for example `vex-nx-<version>.ova`).

## Import (Workstation)

1. (Optional) Delete any older VEX-NX VM so you do not open the wrong one.
2. In Workstation: **File -> Open** -> select the OVA.
3. Before first power-on, review settings:

* **Processors** - enable nested virtualization; raise vCPU if you can.
* **Memory** - raise toward the recommended tier.
* **Network** - three adapters: **Management** / **Internet** / **Lab** (map to VMnet0 / VMnet8 / VMnet1).
* **Hard Disk 1** - expand before you plan a large image library.

4. **Power on** the VM.

## Import (ESXi)

1. Deploy OVF/OVA in Host Client or vSphere Client.
2. Map **Management**, **Internet**, and **Lab** to port groups (UI / uplink / isolated).
3. Set **Expose hardware assisted virtualization to the guest** = ON.
4. Raise CPU/RAM for QEMU labs; power on.

Full ESXi checklist: esxi-import.md.

## First boot timeline

| Time        | What you usually see                                                              |
| ----------- | --------------------------------------------------------------------------------- |
| Early       | Console splash (first install only)                                               |
| Then        | DHCP / Static wizard (**20s** default DHCP). Static waits until you finish typing |
| 1-3 min     | Browser at `http://<ip>/` may show a starting page                                |
| 3-8 min     | Login UI appears (nginx + API)                                                    |
| Later boots | Keep / Change / Reset menu (**20s** default Keep) - see Management network        |
| Background  | Docker/QEMU packages and FRR/Alpine seed can still finish                         |

Use **`http://<management-ip>`** for the first visit. Prefer HTTP until you trust the self-signed certificate. Do **not** use the Docker bridge address `172.17.0.1`.

Full Management IP guide (GUI Static, Keep/Change, examples): Management network.

## Find the management IP

Pick one:

* Guest console MOTD / banner after the network menu
* After login: **Home** or **Infrastructure -> Management network** (live address)
* SSH as `vexnx` / `vexnx`, then `hostname -I` or `ip -4 addr show ens160`

## Scale up after a small import

1. Power the VM **off**.
2. Raise Processors and Memory; expand Hard Disk 1 if needed.
3. Power on. If the guest filesystem did not grow, SSH in and grow the partition (`growpart` + `resize2fs` on Ubuntu-based guests).
4. Open **Infrastructure** and confirm usable CPU/RAM and `/dev/kvm`.

Next: [First login](/vex-nx-user-guide-1/getting-started/first-login.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/getting-started/install-the-ova.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.