Hypervisor hosts and capacity

The Hosts tab at /cloud shows every hypervisor — the TurtiniOS server nodes that can run VMs — and how loaded each one is.

What makes a node a host:
A TurtiniOS server-role node automatically becomes a host the moment it boots with virtualization (libvirt) available. Its agent detects libvirt, advertises the capability to the fabric, and it shows up here — no manual registration. See "Turning a server into a hypervisor."

What each host card shows:
• Online / stale — a green dot means the host has checked in recently; grey means it's gone quiet.
• vCPU — how many virtual CPUs are committed to VMs on this host vs. the host's total cores.
• Memory — how much RAM is committed vs. total.
• VM count — how many VMs currently live on the host.

The capacity bars are what the scheduler reads when you choose "Auto (best fit)." A host that's nearly full won't be picked for a large VM; an empty host will be preferred when balancing (spread) or avoided until needed (binpack).

If the Hosts tab is empty, no server node has advertised virtualization yet. Boot a TurtiniOS server node with KVM/libvirt on the same fabric and it will appear within a few seconds.