Bases and virtual machines
Base images
Section titled “Base images”A base is a verified, read-only template. A VM is a named instance with its own writable disk overlay.
| Base | Suitable for |
|---|---|
| BusyBox | Small command-line programs and quick observation tests |
| Debian 13 with GNOME | Desktop applications and a fuller Linux environment |
Under Add base, choose:
- Download base… for a published bundle. The catalog labels its app compatibility and the app verifies file checksums.
- Import base… for a bundle directory you already have.
- Build base… to build on the host or in a builder VM. This needs additional tools, disk space and build time.
Cancelled downloads keep partial files for resume. Installed older bases may show a newer-base hint. See compatibility before changing bases.
Create and manage a VM
Section titled “Create and manage a VM”Choose New VM, pick a base, and set its name, CPU count, RAM and disk capacity. Debian bases also ask for the guest username and password.
Right-click a VM for rename, duplicate, directory, settings or delete actions. Duplication requires the VM to be stopped. Base deletion is refused while a VM still uses it.
Only one VM runs at a time in 0.3.0. Settings apply on the next boot.
Choose resources
Section titled “Choose resources”Allocate enough RAM for the guest desktop and the program, while leaving memory for the host, Antinomie and recording writes. A GNOME guest has a larger working set than BusyBox.
Start with the catalog’s recommendations and adjust after observing the workload. More virtual CPUs help parallel programs when the host has capacity; they also create more concurrent telemetry. Reducing RAM below a workload’s needs can increase swapping and make it slower.
Disk capacity belongs to each VM’s overlay. Recorded observations need host space in addition to the guest disk. Use telemetry settings to understand buffer and recording overhead.
Display and acceleration
Section titled “Display and acceleration”VM settings provide resolution, fullscreen/fit behavior, acceleration and CPU model choices. Prefer KVM when /dev/kvm is available. Use TCG when hardware virtualization cannot be enabled; it is slower, especially for desktop guests.
QEMU needs its GTK backend for the guest display. The native Antinomie window and the QEMU display are separate windows.
Networking
Section titled “Networking”Networking starts disconnected by default. Enable NAT explicitly when a workflow needs external access or network capture.
A NAT-enabled guest can reach networks available through the host. Choose the analysis environment accordingly. NAT packet capture records the VM interface from the host; it does not require a guest packet-capture helper.