Virtual machines

The current build can create, list, and inspect local machine definitions. Each definition records a name, guest architecture, memory, virtual CPU count, disk path, disk size, and lifecycle state. Definitions are stored in the schema-v2 configuration.

Create a machine

Use New machine from the Dashboard or Virtual machines page. The dialog accepts:

• Name — up to 64 characters. The name cannot contain control characters or /, \, comma, or equals characters.
• Guest architecture — x86_64 only in this build.
• Memory — 256 to 65,536 MiB, and no more than the host reports as total memory.
• Virtual CPUs — 1 to 64, and no more than the host's logical CPU count.
• Disk size — 1 to 1,024 GiB, and no more than the free space reported on the application data filesystem.

Creating a machine requires a Linux x86_64 host, qemu-img, and sufficient free space. The backend validates the input again; the dialog is not the authority. Wave VM creates a private machine directory and a thin-provisioned disk.qcow2 file. It never overwrites an existing disk.

Inspect a machine

The machine list shows lifecycle state, memory, virtual CPUs, disk size, acceleration when running, and any backend error. A missing disk is reported explicitly and disables Start. The details view shows the recorded configuration, disk path, format, availability, and lifecycle actions.

What is not available

• Editing a machine definition after creation.
• Deleting a machine definition or its disk.
• Changing memory, CPU, or disk size.
• Attaching an existing disk or installation media.
• Reset, pause, resume, or snapshots.
• Guest networking or USB passthrough.

Wave VM does not automatically delete VM directories or disks. If a disk is missing, restore it rather than deleting the machine definition.

Continue with Machine lifecycle for start and stop behavior.