User Guide

Graphical console

Connect to the running guest through loopback VNC and noVNC.

Available now

The current build includes a genuine interactive guest console. It connects to the running QEMU process through QEMU's WebSocket VNC transport and renders the guest framebuffer with the bundled noVNC 1.7.0 client.

How it works

QEMU VNC is bound to 127.0.0.1; no public VNC listener is created.
QEMU is configured with WebSocket VNC enabled and a per-run password.
The WebSocket port is discovered through QMP after QEMU starts.
Wave VM generates the console password for each run and keeps it in memory only.
noVNC connects with that password and enables keyboard and mouse input.
The console is available only while the machine is running.

Using the console

Open a running machine and choose Open console. The console view reports connection progress, a security or connection failure, a disconnected session, and a stopped machine. Reconnect is available after a clean or unexpected disconnect. The viewport scales to the console surface.

No guest OS is installed by this build

The console shows the actual guest framebuffer, but the current build cannot install an operating system. A newly created machine may show firmware output or a no-bootable-device message. That is not a simulated console failure; there is no installed guest to boot yet.

Requirements and limits

The machine must be running and tracked by the current desktop process.
The installed QEMU must support WebSocket VNC.
The console is local-only; it is not a remote access feature.
The password is not stored in the VM configuration.
Audio, USB redirection, and multi-monitor controls are not implemented.

Not implemented

Remote console access over a network.
Persistent console credentials or user-managed console passwords.
Guest OS installation or installation-media attachment.
Verified keyboard, pointer, and reconnect behavior across every guest OS.

The console depends on the implemented QEMU lifecycle. See Machine lifecycle and the roadmap.