Quick Start

This section guides you through booting a remote node and running a workload with Mesh Hypervisor after installing the orchestration node (see Installation). Using the default configuration, you’ll boot a remote node via PXE and start a KVM workload with VNC access.

Step 1: Connect a Remote Node

Verify the orchestration node is active:
```
mesh system logview
```
Look for DHCP and PXE activity in the logs.
Connect a remote node to the same Ethernet network:
- Requires x86_64, 2+ GB RAM, PXE support (see Prerequisites).
Power on the remote node and enter its BIOS/UEFI:
- Set network/PXE as the first boot device.
- Save and reboot.

The remote node pulls its kernel and initramfs from the orchestration node, then boots Alpine Linux with a default APKOVL. A unique 8-character UUID is generated during boot using genid machine 8, based on hardware DMI data.

Step 2: Verify Remote Node Boot

On the orchestration node’s console (logged in as root/toor):

List online nodes:
```
mesh node info
```
This shows each node’s UUID (e.g., a1b2c3d4). The UUID is the first 8 characters of a SHA-512 hash of the node’s DMI modalias.
Note the UUID of your remote node.

If no nodes appear, check logs (mesh system logview) for DHCP requests or HTTP downloads (kernel, initramfs). Ensure the remote node’s network port is connected.

Step 3: Start a Workload

Mesh Hypervisor includes a default KVM workload configuration named qemutest1. To launch it:

Use the remote node’s UUID from Step 2 (e.g., a1b2c3d4).
Run:
```
mesh workload start -n a1b2c3d4 -w qemutest1
```
- -n: Node UUID.
- -w qemutest1: Workload name (preconfigured in /host0/machines/default).

This starts a KVM virtual machine with 500 MB RAM, 2 CPU threads, and an Alpine ISO (alpine-virt-3.21.3-x86_64.iso) for installation.

Step 4: Access the Workload

The qemutest1 workload uses VNC for console access:

Identify the remote node’s IP with
```
mesh node info
```
From any system with a VNC client (e.g., vncviewer or TigerVNC):
```
vncviewer 192.168.x.y:5905
```
- Port 5905 is derived from runtime.console.id=5 (5900 + 5).
The VNC session displays the Alpine installer running in the workload.

Next Steps

You’ve booted a remote node and accessed a workload via VNC. See Usage for managing nodes, customizing workloads, or configuring networks.