internal/setup and the CLI command volar setup
Quick install#
The endpoint points to the same script hosted in this repository:Download Volant binaries (volar, volantd, kestrel) from GitHub Releases
Download kernel artifacts: bzImage (from Volant release) and vmlinux (from Cloud Hypervisor)
Install to /usr/local/bin and /var/lib/volant/kernel
Optionally run sudo volar setup
(recommended)
Setup (networking + systemd)#
volar setup
configures host networking and writes a systemd unit for volantd.Host IP in bridge: 192.168.127.1/24
Work dir: /var/lib/volant
bzImage: /var/lib/volant/kernel/bzImage
vmlinux: /var/lib/volant/kernel/vmlinux
Creates bridge vbr0, assigns host IP, brings it up
Adds iptables MASQUERADE for the managed subnet
Writes systemd unit for volantd and enables it
VOLANT_BRIDGE, VOLANT_SUBNET, VOLANT_RUNTIME_DIR, VOLANT_LOG_DIR,
VOLANT_KERNEL_BZIMAGE, VOLANT_KERNEL_VMLINUX, VOLANT_WORK_DIR
Requirements#
qemu-img (from qemu-utils)
bridge-utils (brctl) and iptables
Sudo privileges (or run installer as root)
The installer can auto-install missing packages for Ubuntu/Debian, Fedora, RHEL/CentOS, and Arch-based distros.Verify installation#
If you skipped setup during install, run it later:Uninstall / cleanup#
Stop volantd: sudo systemctl disable --now volantd
Remove bridge and iptables rules manually if you customized them
Remove work directory /var/lib/volant
if desired
Troubleshooting#
If cloud-hypervisor
not found: install package from your distro or upstream
Ensure /proc/sys/net/ipv4/ip_forward
is 1
Check service logs: journalctl -u volantd -f
Networking conflicts: ensure vbr0
bridge does not collide with existing networks
Modified at 2025-10-05 17:45:39