中文日本語

FAQ

Frequently asked questions

With so many virtualization hosts around, why another one?

Because none of them keeps a VM running while the host system is upgraded and restarted, and none of them can even suspend a VM that owns a passed-through device. On one box the host is also the NAS, the router and the desktops, so every host update stops everything. The data-centre answer, a second machine and shared storage, is not an answer for one box.

keelOS puts a small hypervisor (about 100 KB) under FreeBSD and bhyve. It holds the VMs' memory, their CPU state and the IOMMU, and it does not restart with the host: the VMs pause for about 25 seconds and carry on, passed-through devices included. Everything around it is standard on purpose (FreeBSD, bhyve, OpenZFS, virtio), so nothing locks your VMs in.

We measure against KVM and publish the numbers, the gaps included: why keelOS, the feature comparison and the benchmarks.

Is it for a home server, a small office or a data centre?

All three, with a setup for each. One machine at home runs the NAS, the router and a few desktops, and keeps them running through host restarts. A small office adds a management VM that watches its hosts from one page, with alerts and reports. A data centre runs rows of hosts under the same management VM and moves VMs between them: today with a short stop (cold migration); live migration is being built. The image, the web interface and the API are the same in every case.

What keelOS does not do: shared storage, failover clustering, software-defined networking and multi-tenancy. Each host owns its VMs on its own disks.

Does it run on AMD?

Early. Since release keelos-37d6fbc (2026-10-14) guests run under the keel hypervisor on AMD (SVM and NPT), tested on one Ryzen mini PC (Lenovo M75q) with Linux and Windows 10 guests. Not on AMD yet: keeping the VMs running through a host restart, PCIe passthrough and SR-IOV, and the integrated GPU. An EPYC server is the next test machine; the release notes say what changes.

Does it run on an N100 / N305 mini PC?

These are Intel CPUs with VT-x and VT-d, so they should; we have not tested one yet. See the hardware page for what we have tested and what we expect.

My machine is not powerful and I only want to run containers. Is that supported?

Yes. On the kcell page you pick one of 18 app templates (Jellyfin, Nextcloud, Immich and others) or paste a Docker Compose file, and keelOS makes a kcell for it by itself: a small Linux VM with its own kernel and Docker, with nothing to fill in. Its volumes are datasets on the host, its ports are published on the host's own address, and stopping it saves a checkpoint, so it comes back where it was. A kcell for one small service needs a few hundred MB of memory; keelOS itself runs on an 8 GB machine.

Early: custom Compose files work, and more templates are coming. The CPU still needs VT-x, because a kcell is a VM. On 12th generation and newer Intel CPUs a kcell can get a slice of the integrated GPU for video transcoding. Docker is not installed on the host itself.

Can I pass a GPU to a VM?

Yes. The Intel integrated GPU goes to a VM with the monitor on the host's HDMI port and the host's keyboard and mouse: UHD 630 (8th to 10th generation, Lenovo P340 Tiny and P330 Tiny) to Windows 10, and UHD 770 (12th generation, Core i5-12600K) to Windows 10 and Linux. A discrete card (GeForce GTX 1080 Ti) goes to Linux and Windows 10 VMs. On 12th generation and newer Intel CPUs the integrated GPU (UHD 770 tested) is split with SR-IOV so that several VMs share it: a Windows VM with a virtual display and a Linux VM doing hardware video transcoding run on virtual functions today. Other cards have not been tested; see the hardware page. AMD graphics are not supported yet.

How often does a hypervisor upgrade need a full restart with the VMs shut down?

Only when the hypervisor itself changes. It is kept small (about 100 KB) so that this is rare; the release notes say for each release whether it changes the hypervisor. Upgrades of the host system (FreeBSD, drivers, ZFS, the management program) only pause the VMs.

Can I move VMs to another machine?

Yes, from the management VM: tick the VMs, pick the host. A VM is stopped, its dataset is sent over the network, and it starts on the other host; a small Linux VM was down for 2 to 2.5 seconds over 10 GbE, and the networks are mapped to the target's, with a check before the move. The copy on the source is kept for 24 hours so the move can be taken back. By hand it is still zfs send.

Moving a VM while it runs (live migration) is being built. Its first piece, moving a running VM between the pools of one host, pauses the VM for well under a second in our tests. Intel and AMD hosts can exchange VMs only stopped.

How do I back up VMs?

Snapshots in the web interface cover a VM's disks, settings and firmware variables. Copy them to another machine with zfs send. Scheduled snapshots and backups to another host are planned.

Why is traffic between two VMs on the same host slower than on KVM?

keelOS's virtio network runs in bhyve's user-space process; KVM's runs in the kernel. Between two VMs on one host keelOS reaches about 7.5 Gbit/s against KVM's 31 Gbit/s: still more than a 1 or 2.5 GbE network, but behind. For a router VM and a NAS VM on one machine, give both an SR-IOV virtual function of the same network card: the card switches the traffic in hardware. On a 10 GbE link to another machine a VM already sends at line rate.

A switch in the kernel (netmap's VALE) is being built into keelOS. Measured by hand it carries 24–27 Gbit/s between two VMs on one host, against KVM's 27–31 on the same machine.

Is there a changelog and a roadmap?

Every release comes with release notes on GitHub Releases. The planned items are the ones marked planned on this site; there is no dated roadmap yet.

How do I hear about new releases?

On the releases repository, choose Watch → Custom → Releases, or subscribe to its feed. A new release comes out about every week.

About keelOS →