Settings
Updated
Settings covers the host itself rather than the machines running on it.
Administrator
Section titled “Administrator”Change the administrator password. The host has one administrator: the same password signs in to the console and to the host itself (console, SSH, sudo), so changing it changes both. Other sessions are signed out.
Virtainer web interface
Section titled “Virtainer web interface”The console is served on the default HTTP port, so its address needs no port number. You can move it to another port here.
SSH access
Section titled “SSH access”Turn SSH access to the host on or off. With it off, reach the host through the console or its serial console.
Direct SSH login as root is off on every host, new installs included, whatever
this switch says. The administrator account is the host’s only shell login, and the
Diagnosis tab reports a failure if the SSH server ever permits root login.
This controls access to the host, not to the machines running on it. Those have their own SSH, configured through cloud-init.
Set the host’s persistent swap size in whole GiB: 4 GiB by default, or 0 to disable it. Settings shows the configured size, active size and amount used. Changes apply immediately and survive a reboot. The limit is 64 GiB and no more than half the currently free disk space. Shrinking or disabling swap is refused if RAM cannot absorb it; a failed change restores the previous swap.
Swap does not increase the memory available for allocating VMs; that capacity is still based on physical RAM. Host Information and Diagnosis also show swap status and application failures.
VM autostart
Section titled “VM autostart”Controls what happens to machines after the host reboots.
| Setting | Behaviour after a reboot |
|---|---|
| On (default) | Machines that were running are started again automatically |
| Off | Machines that were running come back stopped, ready for you to start |
This restores the last running state; it is not a hand-maintained boot order. Machines you stopped yourself are never started for you either way. See After a host reboot.