Skip to content

BliKVM Setup

Experimental

BliKVM support is Experimental. BliKVM runs the same kvmd stack as PiKVM, so the agent uses the full kvmd console path.

How to connect a BliKVM device to KVM Fleet.

Prerequisites

  • BliKVM (CM4, v3, or PCIe) running its bundled PiKVM-OS / kvmd
  • SSH access to the device
  • A kvmd password set (not the factory default — the installer refuses to proceed if admin/admin is still active)
  • An enrollment token from the dashboard

Install the agent

Like PiKVM, BliKVM's root filesystem is read-only by default; the installer remounts it automatically. Pass --device blikvm so the device is labelled correctly in your fleet:

curl -sSL https://app.kvmfleet.io/install | sh -s -- \
  --token <your-token> --device blikvm --kvmd-pass <your-kvmd-password>

The agent installs to /usr/local/bin/kvmfleet-agent; state lives in /var/lib/kvmfleet/.

Console access

Because BliKVM runs kvmd, KVM Fleet proxies the full web UI through the agent's outbound tunnel — video, keyboard, mouse, ATX power, and mass storage, all in the browser. No inbound ports.

Network considerations

The agent makes only outbound HTTPS connections to app.kvmfleet.io on port 443. No inbound ports need to be opened.

Troubleshooting

Symptom Fix
Agent won't start Check journalctl -u kvmfleet-agent -f
Device shows offline curl -I https://app.kvmfleet.io from the device
Console won't load Ensure kvmd is running: systemctl status kvmd
Installer rejects default password Set a real kvmd password: kvmd-htpasswd set admin