Configuring Workloads

Workloads in Mesh Hypervisor are KVM virtual machines running on remote nodes, configured and managed from the central orchestration node. This section covers creating and controlling KVM workloads using config files and mesh workload commands. The orchestration node is CLI-only (no GUI); access VMs via tools like VNC from another machine. For bare-metal tasks, see Configuring Groups.

Prerequisites

  • Remote nodes are online (check with mesh node info).
  • Central node is running (mesh system start executed).

Commands and edits run from the central node’s console.

Creating a Workload Config

KVM workload configs are stored in /var/pxen/monoliths/ on the central node. Each file defines a VM, uploaded to nodes when started.

Example: Create /var/pxen/monoliths/qemutest1.conf:

name=qemutest1
uuid=qweflmqwe23
platform.volume.1.source=http://host0/isos/alpine-virt-3.21.3-x86_64.iso
platform.volume.1.type=iso
platform.volume.1.path=/tmp/alpine.iso
platform.memory.size=500M
platform.cpu.threads=2
platform.cpu.mode=Penryn-v1
runtime.console.type=vnc
runtime.console.id=5
  • Sets up a VM with an Alpine ISO, 500 MB RAM, 2 threads, and VNC access.

Managing Workloads

Use mesh workload with a node UUID (from mesh node info) and workload name matching the config file (e.g., qemutest1).

Commands

  • Download Resources:

    mesh workload download -n a1b2c3d4 -w qemutest1

    Fetches the ISO to /tmp/alpine.iso on the node. Add -f to force redownload.

  • Start:

    mesh workload start -n a1b2c3d4 -w qemutest1

    Uploads qemutest1.conf to the node and launches the VM.

  • Access:

    vncviewer <node-ip>:5905

    From a separate machine with a VNC viewer (e.g., TigerVNC), connect to the console (port 5900 + id=5). Find <node-ip> in mesh system logview.

  • Stop:

    mesh workload soft-stop -n a1b2c3d4 -w qemutest1

    Gracefully stops the VM. Use hard-stop to force it.

  • List:

    mesh workload list -n a1b2c3d4

    Lists running workloads on the node.

Notes

  • Configs upload on start, stored in /var/pxen/monoliths/ on nodes after.
  • Workloads need node resources (RAM, CPU); check Prerequisites.
  • Snapshot commands (e.g., snapshot-take) are KVM-only—see The mesh Command.
  • Full syntax is in Workload Config.

Next, see Network Configuration or Configuring Groups.