中文日本語

Compare

What keelOS does, next to the others

One row per feature, including the ones keelOS does not have. Yes means it is in the product today; partial means it works with conditions, by hand, or through third-party pieces. Checked on 2026-10-15 against each product's current documentation; if a cell is wrong, write to [email protected] and we fix it.

keelOSProxmox VE 9ESXi 8Hyper-V (Windows Server 2025)Unraid 7TrueNAS 25
Host restarts and upgrades
Host system upgraded and restarted while the VMs keep running in memoryYespause of about 25 s; TCP connections stay upNoshut down, or suspend to disk by handNosuspend to disk, resume afterNosaved to disk, restored afterNoshut down, or hibernated by the guestNoshut down, started again
A VM with a passed-through device kept through a host restartYesthe hypervisor runs the IOMMU; the device keeps its DMA mappingsNoNocannot be suspendedNoSave is not allowed with DDANoNo
Hypervisor part that must restart with the VMs downYesabout 100 KB; rarely changesNothe whole systemNothe whole systemNothe whole systemNothe whole systemNothe whole system
Upgrade with rollback to the previous versionYestwo boot slotsPartialapt; rollback by handYesprevious bootbankPartialuninstall the updateYesprevious version restoreYesboot environments
Devices
PCIe passthrough of a whole device: disk controller, NVMe drive, network cardYesdevices listed by serial number, held before the host's driversYesYesDirectPathYesDDA, Windows Server onlyYesYesexperimental in 25.04
SR-IOV virtual functions of a network card for VMsYesIntel X710, X550, X540, I350YesYesYesPartialby handPartialby hand
Intel integrated GPU to a VM, with the host's monitor, keyboard and mouseYesUHD 630 and UHD 770; Windows 10, LinuxYesPartialnot supported by VMware; works on some boardsNoYesPartialexperimental in 25.04
Intel integrated GPU shared by several VMs (SR-IOV, 12th generation and newer)YesUHD 770; driver in the product; Windows and Linux VMsPartialthird-party DKMS module, rebuilt for each kernelNoPartialGPU-P on client Hyper-V, unsupported on ServerPartialcommunity pluginNo
Discrete graphics card to a VMYesone card tested: GeForce GTX 1080 TiYesYesYesDDA, Windows Server onlyYesPartialexperimental in 25.04
Host CPU and disk temperatures shown inside the guest by standard sensors, no agentYesNoNoNoNoNo
Guest desktops on the host's own monitor, switched with Ctrl-Alt-F2…F12, without passing a GPUYesNoNoPartialVMs in windows on the host's desktopNoNo
Guests
Windows 11 with a virtual TPM and Secure Boot, without workaroundsYesBitLocker works; TPM state survives host restartsYesYesYesPartialTPM yes; Secure Boot reported to need other firmware filesPartialTPM option; state loss reported on 25.10
Windows XP, Server 2003 and Windows 7 with their in-box driversYesSeaBIOS; IDE, PCnet, UHCIYesYesYesgeneration 1 VMsYesPartiallegacy boot in Incus by hand
Nested virtualization: Hyper-V and WSL2 inside a Windows guestYesfrom the next releaseYesYesYesYesPartialno documented option
RDP to the VM's console from any RDP client, with sound and clipboard, no guest agentYesthe host answers RDP for every VMNonoVNC, SPICENobrowser console, VMRCYesenhanced session, Windows guestsNoVNCNoVNC, SPICE
Docker and other lightweight containers run directly, next to the VMsYeskcells: keel makes a small Docker VM per app from a template or a Compose file; earlyPartialLXC; Docker inside a container or VMNoPartialWindows containersYesDockerYesDocker apps
Memory and storage
Unused guest memory given back to the host without overcommitYeszero pages reclaimed and lent as disk cache; returned on the first writePartialballooning, KSM: overcommitPartialpage sharing, ballooningPartialdynamic memoryNoNo
ZFS under the VMs: snapshots, checksums, send and receiveYesone dataset per VMYesNoVMFSNoNTFS, ReFSYesZFS pools since 7.0Yes
A VM snapshot covers its disks, settings and firmware variablesYesYesYesYescheckpointsPartialPartial
Management
Web interface, command line and an HTTPS API with scoped tokensYesEnglish, Chinese, JapaneseYesYesYesPowerShell, Windows Admin CenterYesGraphQL API since 7.2Yes
Several hosts managed from one placeYesa management VM; no cluster, no quorumYescluster; Datacenter Manager across clustersPartialvCenter, paidYesWindows Admin Center, SCVMMNoNo
Cold migration between hosts from the web interfaceYes2–2.5 s downtime for a small VM; can be taken back for 24 hYesPartialvCenterYesNoNo
Live migration between hostsBeing builtrunning VMs already move between pools on one hostYesPartialvMotion, paidYesNoNo
Shared storage and failover clusteringNonot planned: each host owns its VMsYesYespaidYesNoNo
Ready-made VM packages from a catalogue: NAS, accounts serverYesMarket: keelNAS, keelAuth, signed packagesPartialcontainer templatesPartialOVA importNoPartialDocker apps, not VMsPartialDocker apps, not VMs
BMC (IPMI) settings from the web: network, fan modes, usersYesNoNoNoNoPartialIPMI network
Host health page: CPU, memory and disk scores, temperature curves, crash detectionYesPartialgraphs, no scoresPartialhardware healthPartialperformance monitorPartialtemperatures by pluginPartialSMART, reports
Platform
AMD CPUsBeing builtearly: guests run; no passthrough, no restart with VMs yetYesYesYesYesYes
Open sourceNothe VMs use only standard formats, see AboutYesAGPLNoNoNoYes
Licence and priceYesfree for personal use; commercial use with our permissionYesfree; paid enterprise repository and supportPartialfree 8.0 U3e edition; vSphere paidPartialwith a Windows Server or Windows Pro licenceNopaid licenceYesfree Community Edition

Product names belong to their owners. The keelOS column says what the current release does; the feature pages and the release notes have the details and the measurements.

Sources

Why keelOS → · Frequently asked questions →