User Guide
User Guide
What is usable today and what is not implemented yet.
The current desktop build implements a real local VM lifecycle. It can create a machine definition and a blank QCOW2 disk, start and stop a QEMU process, and open the running guest display in a loopback noVNC console. It is not yet a complete virtual machine manager.
Usable today
- Inspect the host operating system, architecture, logical CPU count, and memory.
- See free and total space on the application data filesystem.
- See whether QEMU and qemu-img were found, and which version was parsed.
- See whether Linux KVM is available, inaccessible, or unsupported.
- See the application data directory and configuration path.
- Create a machine definition with a validated name, memory, vCPU count, guest architecture, and disk size.
- Create a thin-provisioned QCOW2 disk with qemu-img.
- Start and stop a real QEMU process with QMP lifecycle control.
- Open the running guest display in an interactive console.
- Inspect saved machines, disk presence, acceleration, and lifecycle state.
Read Virtual machines for creation and inspection, Machine lifecycle for start and stop behavior, and Graphical console for the guest display.
Not implemented
- Installing a guest operating system or attaching installation media.
- Selecting or verifying ISO images, or downloading operating system images.
- Editing or deleting a machine definition.
- Resetting, pausing, or snapshotting a machine.
- Configuring guest networking.
- USB passthrough.
- Windows or macOS host support.
- Public releases, installers, or checksums.
A running machine is not an installed guest
Current scope
Machine creation and lifecycle operations require a Linux x86_64 host and support x86_64 guests only. QEMU and qemu-img must be installed. KVM is optional; without verified acceleration, QEMU uses software emulation (TCG).
The Disks and installation media page explains what storage exists today and what remains planned.