Skip to main content

Integrations

Integrations are enabled with environment variables on the controller. Atlas is off by default.

Atlas storage​

Puts VM disks on Ceph RBD, NFS or ZFS volumes managed by the Atlas storage control plane, with snapshot, backup and restore.

ATLAS_ENABLED=1
ATLAS_BASE_URL=http://127.0.0.1:5110
ATLAS_TOKEN=<service-account JWT>

Create a VM on Atlas storage by passing atlas_root_disk: true to POST /api/v1/vms.

GuestKit​

GuestKit's in-guest agent reports guest health, checks VMs offline before migration, and enforces per-container eBPF policy inside guests. Machina talks to it through the QEMU guest agent; see Guest policy. Controller-side features are on by default (GUESTKIT_ENABLED=true).

Networking and security​

Network enforcement and observability are built in, not integrated: Machina's own eBPF service, machina-bpfd, replaces Cilium, Tetragon, Netra and PacketWolf, and Machina no longer talks to any of them. See Native eBPF.

FluxVM​

A second VM backend next to libvirt: VMs on QEMU, Cloud Hypervisor, Firecracker or flux-vm from a host's fluxvm-api appear with backend: "fluxvm". Enable it on the daemon with [fluxvm] enabled = true and on each host's agent with MACHINA_FLUXVM_URL. Snapshots, backups (every engine; running VMs on QEMU), hot-add (QEMU, Cloud Hypervisor), extra NICs and install ISOs (QEMU), consoles, live migration and HA re-create (QEMU on a shared disk) are covered in the FluxVM guide.

Containers and Kubernetes​

  • Containers. Local Podman or Docker containers and Podman pods run next to your VMs (configure the socket in [vessel]).
  • KubeVirt. Inventory of KubeVirt VMs and a documented migration path.

Migration into KVM​

hyper2kvm converts guests from other platforms into KVM; GuestKit checks them offline before cutover.

Automation​