VMBook OS · implemented bare-metal MVP

A thin bare-metal node for the VMBook fleet.

Debian 13 supplies the kernel and hardware reach. QEMU/KVM runs machines. ZFS manages local storage. vmbook-server connects the node to the same site-aware control plane used for desktops and remote hosts.

VMBook control planevmbook-server · local TLS APIQEMU / KVM · ZFS · Linux networkingDebian 13 · Linux 6.12 driversBare x86-64 server hardware

Evidence before marketing

The bare-metal MVP is implemented.

The repository contains the realized two-stage image builder and BIOS/UEFI installer ISO builder. The generated node is branded VMBook OS and self-provisions its service and storage. Public release packaging and a published multi-hardware validation matrix remain the next stage; that distinction does not erase the implemented MVP.

Implemented
Bootable raw image and BIOS/UEFI installer build paths
Base
Debian 13, QEMU/KVM, ZFS and a static vmbook-server
Release stage
Implemented MVP; public validation and distribution pending
Not claimed
Cluster HA, quorum, fencing or automatic failover

What the build already does

Small operating-system delta. Explicit management boundary.

01

Broad boot support

The initramfs uses MODULES=most so one image carries common AHCI, NVMe, SAS and RAID storage drivers instead of inheriting only the build host’s devices.

02

Hardened transport

The API binds to localhost. Management reaches it through a restricted SSH tunnel and still pins the VMBook TLS identity inside that tunnel. Password and interactive console login are disabled in the current appliance posture.

03

Storage-aware first boot

The node loads ZFS, creates a tuned vmpool on an eligible spare disk and starts vmbook-server. Provisioning is recorded only after pool creation succeeds.

04

Hardware evidence

SMART, NVMe, DMI, PCI and IPMI tools provide vendor-neutral health information. Proprietary RAID/BMC suites are intentionally not redistributed.

Architecture decisions

Where VMBook OS stops.

It is not a new hypervisor.

KVM and QEMU provide virtualization. VMBook OS is a thin node appliance and management integration, not a replacement CPU virtualization engine or a fork of Debian.

ZFS is the current local-storage foundation.

Compression, checksums, snapshots, clones, ARC and optional L2ARC/SLOG come from OpenZFS. VMBook should manage and tune these capabilities rather than claiming to have invented another storage engine.

Inventory is not HA.

Seeing nodes in one fleet does not provide shared storage, quorum, fencing or automatic failover. Those require separate implementation and failure testing.

Bare metal is an option, not a requirement.

VMBook continues to manage Windows, Linux, macOS and provider-owned workloads. VMBook OS is the controlled-node path for organizations that want a dedicated KVM host.

Planned release path

  1. Build reproduciblySigned image, installer and update artifacts.
  2. Test real hardwareStorage, NIC, boot, BMC and recovery matrix across server generations.
  3. Publish safety proceduresInstall, enrollment, disk selection, rescue and rollback.
  4. Release with limitsState exactly which clustering and storage capabilities are absent.