Skip to content

Create a Workload

A Workload is a VM running on one Device. Create it from the Home dashboard even when it will run on another Device.

  1. Open the Home console (http://<dashboard-device>:7777).
  2. Click Create VM.
  3. Pick what to run from the template gallery, Windows, or your own Library image.
  4. Name the VM, pick the Device, size, and disk options in the 3-step Create VM dialog (Gallery → Configure → Disk).
  5. Create. Provisioning on a member Device is proxied through Home. The phone does not connect to the member’s IP.

Windows on arm64 Devices uses the windows-arm64 guest (UEFI, TPM, virtio-win). Windows on x86_64 is a guest profile in progress (windows-amd64); Linux guests already run on both arches.

  • Catalog downloads follow this Device’s architecture. You can still download the other arch when you will deploy it on a matching Device.
  • A missing Library copy on the target Device is a placement warning, not a silent skip.
  • Optional: set a custom Library directory in Settings.
  • Settings → Library and the Images page show used/free for that Library path’s volume. It can differ from the data dir. Depot Device offline is an empty/error state, not zeros.
  • New disks use the Device’s default VM disk directory (Device page).
  • On Linux, Create Disk can attach a host block device as raw. Mounts, swaps, and devices the host already uses stay blocked. The Device’s barkvisor user needs the disk group (barkvisor.service.d/disk.conf). macOS has no block-device option.
  • GPU list labels NVIDIA, Intel, and AMD. Several cards of the same vendor stay listed separately.
  • GPU attach is the existing passthrough path (IOMMU / vfio-pci / KVM). Fail closed if that is not ready. Linux host setup: GPU passthrough.
  • Workload detail also has a PCI picker for other VFIO devices. The boot disk and the last remaining uplink stay excluded. The picker is hidden on macOS.

The Workload lives in that Device’s SQLite. Start, stop, and console from the Device detail page. If that Device is unreachable, the dashboard says so — it does not invent counts, and Workloads on other Devices keep running.