Causes and remedies for the error codes of hosts: memory, capabilities, maintenance mode and removal.
error.host.insufficient_memory
Text in the console
Host {host} has {available} MiB of memory free for virtual machines; this one needs {requested} MiB. Power off other virtual machines, give this one less memory, or move it to another host.
Meaning for API clients
Power-on refused: the host has available MiB free for virtual machines, the guest needs requested.
the memory in MiB that the host has free for virtual machines.
host
the name of the host.
Cause. Power-on was refused, because the host has less memory free for virtual machines than the virtual machine needs. Free memory is the memory of the host, minus the reserve that the host keeps for itself (host_memory_reserve_mib in the [vm_ops] section, 2048 MiB by default), minus the memory of the virtual machines that run on it. The setting memory_overcommit_ratio in the same section allows the running virtual machines to exceed that amount; its default of 1.0 means no overcommit.
Remedy.
Power off virtual machines that are not needed on that host: kyvernon vm power-off <id>.
Give the virtual machine less memory: Edit settings.
Move the virtual machine to a host with more free memory: kyvernon vm relocate <id> --host <host>.
error.host.not_in_maintenance
Text in the console
Host {host} is not in maintenance mode. Enter maintenance mode first, or force the reboot or shutdown.
Meaning for API clients
Reboot or shutdown needs the host in maintenance mode (or force).
Cause. A reboot or shutdown of a host was asked for while the host is not in maintenance mode. A host in maintenance mode runs no virtual machines, so nothing stops with it.
Remedy.
Enter maintenance mode first: kyvernon host enter-maintenance <id> --wait. In the console, use Enter maintenance mode.
Then reboot: kyvernon host reboot <id>, or shut down: kyvernon host shutdown <id>. In the console, use Reboot.
When the virtual machines on the host may stop with it, force the action: kyvernon host reboot <id> --force.
error.host.not_connected
Text in the console
Host {host} is not connected to the control plane. Retry when it is connected again.
Cause. The operation needs the host agent, and the host is not connected to the control plane: it is disconnected by an administrator, not responding, or still waiting for its agent to register.
Remedy.
Look at the connection state of the host: kyvernon inventory host <id>.
A host that an administrator disconnected comes back with kyvernon host reconnect <id>.
A host that does not respond needs its agent running and the network to the controller: check the service kyvernon-agent on the host.
error.host_capability_missing
Text in the console
The host does not offer the capability {capability}. Choose another host, or update the host agent.
Cause. The operation needs a capability that the host did not declare. Suspending a virtual machine needs suspend-to-disk, changing the vCPUs, memory or devices of a running virtual machine needs hotplug, and live migration needs live-migration on both hosts.
Remedy.
Choose a host that offers the capability. The capabilities of a host are in its record: kyvernon inventory host <id>.
Update the host agent to a version that declares the capability, then reconnect the host.
For a change to the vCPUs, memory or devices, power the virtual machine off first.
error.host_has_running_vms
Text in the console
The host still has running or suspended VMs; power them off or evacuate first
Meaning for API clients
Maintenance mode needs the host's VMs powered off or moved.