# Setting up the Proxmox Nodes
On the first page of this chapter, we defined our requirements and made some key decisions. Now, let’s set up the Proxmox nodes in VirtualBox and install Proxmox VE on them.
[](https://wiki.zn80.net/uploads/images/gallery/2026-03/scaled-1680-/grafik.png)
To ensure cluster stability and prevent traffic saturation, your test environment requires a minimum of three separate network interfaces:
- **Management Interface:** For host access and configuration.
- **Cluster Communication (Heartbeat):** Isolated traffic for node health and HA voting.
- **VM Migration & Storage Replication:** High-bandwidth link for data synchronization.
> **Note:** While dedicating a network segment for NAS storage is a best practice in production, it is excluded from the scope of this virtualized test exercise.
## Creating the Master Virtual Machine (Hardware Mode)
To avoid missing critical settings or having to restart the process, it is recommended to build a single VirtualBox Virtual Machine (VBVM) to act as a template. You can name this master image `proxtpl` so that it remains at the bottom of your VM list. **Ensure that you never actually start the master image; it must remain powered off.**
- **Name:** `proxtpl`
- **Type:** Linux, Debian (64-bit)
- **RAM:** 2 GB minimum (4 GB or 6 GB is recommended if your host hardware allows).
- **Storage (SATA0):** Create a 32 GB boot drive for the Proxmox installation.
- **Storage (SATA1 & SATA2):** Create two 32 GB dynamically allocated disks; these will be used for the ZFS storage pool. You may use 64 GB if you have sufficient space.
- **Boot Order:** Adjust the order to set **Hard Disk** first and **Optical** second.
- **Optical Drive:** Mount the Proxmox ISO.
- **Network Adapters:** Attach 3 adapters:
- **nic0:** BRIDGED (Management interface)
- **nic1:** HOST-ONLY (Cluster interface / Core sync) — **Disable DHCP**
- **nic2:** HOST-ONLY (Replication / Migration interface) — **Disable DHCP**
Once configured, your setup should look like this:
[](https://wiki.zn80.net/uploads/images/gallery/2026-03/5d424ef4-3ee5-4fc9-81cc-4ce2b4252d91.png)
Once the master is configured, create three clones and name them `prox01`, `prox02`, and `prox03`.
## Installing Proxmox VE (Software Mode)
With your three clones created, start them up to begin the installation.
- **Ignore KVM Virtualization errors:** You will likely see an error stating that KVM Virtualization is not detected. This is expected, as VirtualBox may not pass VT-x/AMD-V instructions through to the guest. This is not an issue for this lab, as **the test cluster will run Linux Containers (LXC)** instead of full VMs.
- **Verify hostnames:** Ensure you correctly name each node (e.g., `prox01.local`, `prox02.local`, `prox03.local`) during setup. Renaming a node after a cluster is established is a complex and difficult procedure.
- **Select the 32GB boot drive** for the installation target.
- **Configure sequential IP addresses:** Base these on the hostnames to simplify management (e.g., `prox01` – 192.168.10.201, `prox02` – 192.168.10.202, `prox03` – 192.168.10.203).
- **Network Settings:** Set the Netmask to `255.255.255.0` or use CIDR notation (e.g., `192.168.10.201/24`).
- **Gateway:** Set this to your network's gateway, most likely `192.168.10.1`.
- **DNS Server:** Set this to your local DNS configuration, also likely `192.168.10.1`.
- **Finalize:** After installation, shut down the hosts and **reboot them in headless mode**. This is where the boot order change from earlier comes in handy.
[](https://wiki.zn80.net/uploads/images/gallery/2026-03/scaled-1680-/dc80617e-4ef6-4a60-a2ef-294b42277024.png)
Unfold to see predefined IP Configuration
Remember the IP Configuration from the [Overview-Page](https://wiki.zn80.net/books/proxmox-ve/page/overview#bkmrk-network-configuratio):
{{@387#bkmrk-node-1%3A-nic0-192.168}}