Become a Beta Tester

DocsServers and Sensor

Install Checks

What Frabs checks on every server before you confirm.

Every install runs the same fixed checks, from the facts the sensor reported. Each shows passed, warning, note or failed on the review screen; open the ⓘ for the detail. A failed check blocks confirming.

The checks

CheckWhat it provesIf it does not pass
Platform identifiedA supported platform was foundFailed: nothing to attach to
Guest list readEach platform's own guest list was read successfully, even if it is emptyFailed: the reason is shown (for example /etc/pve not mounted). Fix it, then Reconnect
Guests foundVMs and containers, counted separatelyShown for you to compare with what you run
Leftover configs ignoredOld configs that are not guests here (for example stale /var/lib/lxc on Proxmox) were not countedNote only
Running guests with an interfaceEvery running guest has a network interface on the hostWarning: those guests cannot be watched until one appears
NICs the host cannot seeNo passthrough, SR-IOV, macvlan or direct NICsWarning: traffic on those NICs bypasses the host and cannot be watched or limited
Only VM interfaces watchedNo bridge, bond, VLAN or uplink is on the watch listFailed: the plan is rejected
Interfaces without a known guestEvery VM-like interface belongs to a known guestWarning: traffic is counted, but no automatic action is ever taken against it
Routed containers (venet0)Legacy OpenVZ containers share venet0Note: matched by each container's own IPs
Open vSwitchOVS is in useWarning: check every VM port is listed
Cluster / poolThis server's cluster and its other nodesNote: install Frabs on every node with customer guests
Panel backendFor Virtualizor, VirtFusion and SolusVM, guests are read from the hypervisor underneath, not the panelNote
Kernel supportThe nftables hooks the sensor needs (Linux 4.2+)Failed: upgrade the kernel

What each platform must prove

PlatformChecked
Proxmox VEProxmox's own guest list for this node (even if empty); VMs and containers apart; stale LXC ignored; cluster known; each guest's tap or veth on its bridge
libvirtvirsh answered; each VM by its UUID; interfaces from libvirt's live state; passthrough and SR-IOV flagged
VirtFusion, Virtualizor, SolusVMThe hypervisor underneath read (libvirt, Xen or OpenVZ); each VPS matched to a running guest on this node
OpenVZvzlist answered; bridged and routed containers told apart
Virtuozzoprlctl answered for VMs and containers; NICs matched by MAC
LXCEach container from lxc-ls confirmed by lxc-info; leftovers ignored
LXD, IncusThe API answered; macvlan, SR-IOV, physical and OVN NICs flagged
Xen, XCP-ngxl answered; each domain by its UUID (domain IDs change on restart); vif interfaces found