NanoKVM Setup
Experimental
NanoKVM support is Experimental. The Sipeed NanoKVM doesn't run kvmd,
so the agent fronts its native web UI in raw reverse-proxy console mode.
How to connect a Sipeed NanoKVM device to KVM Fleet.
Prerequisites
- Sipeed NanoKVM (Cube or PCIe) reachable on its local web UI
- SSH access to the device
- An enrollment token from the dashboard
Install the agent
The installer detects NanoKVM automatically (it looks for the /kvmapp
firmware partition). You can also force it with --device nanokvm:
If your NanoKVM web UI requires a login, pass those credentials so the agent can authenticate the proxied console:
The agent installs under /kvmapp/kvmfleet/ (NanoKVM's writable partition).
Console access
KVM Fleet wraps NanoKVM's own web console behind the platform's access governance and audit trail, then proxies it through the agent's outbound tunnel. Every session is gated by your JIT policy and recorded in the audit log.
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 the agent log under /kvmapp/kvmfleet/ |
| Device shows offline | curl -I https://app.kvmfleet.io from the device |
| Console shows "device console unreachable" | Confirm the NanoKVM web UI is up on http://localhost and re-run with the right --kvmd-user/--kvmd-pass if it needs auth |