From Proxmox to FreeBSD and Sylve in Our Office Lab
This company swapped their office lab's virtualization stack from Proxmox to a custom FreeBSD and Sylve setup, seeking a lighter, more workflow-aligned infrastructure. The move was driven by a need for efficiency in repetitive development and testing tasks, rather than a failing system. On Hacker News, the discussion dives into the practicalities of bhyve and its comparison to KVM, particularly regarding feature parity like nested virtualization.
The Lowdown
IP Technics, a company focusing on IT solutions, detailed their decision to transition their internal office lab's virtualization environment from Proxmox to a bespoke stack built on FreeBSD and Sylve. This strategic shift wasn't a reaction to system failures but a proactive measure to streamline their infrastructure and align it more closely with their specific, often repetitive, operational demands.
- The existing Proxmox setup, while functional for many clients, felt increasingly cumbersome for their internal workflow, which involved frequent VM provisioning, storage adjustments, and hardware passthrough for testing custom Linux distributions.
- They found FreeBSD's core primitives (ZFS, bhyve, jails, pf, VNET) to be exactly what they needed, with Sylve providing an intuitive management layer that didn't over-engineer solutions.
- The new stack brought significant efficiency gains, including simplified ZFS operations (snapshots, replication), readily accessible hardware passthrough via the UI, on-the-fly VM disk image conversion, and reliable distro image downloads via torrent.
- The goal was not a grand architectural overhaul but a proportionate, stable, and direct infrastructure that reduced cognitive load and friction in daily tasks.
This migration underscores a growing preference among some technical teams for lean, purpose-built infrastructure solutions that prioritize operational fluidity and directness over feature bloat, particularly when a "cloud-native" approach isn't the best fit for their unique blend of development and testing requirements.
The Gossip
Bhyve's Burden: Nested Virt Woes
Commenters acknowledged FreeBSD's appeal but immediately raised concerns about `bhyve`'s feature set compared to Linux's `KVM`, specifically highlighting the absence of nested virtualization. This limitation was deemed crucial by some, preventing the execution of certain hypervisor-dependent systems like Qubes OS or Windows VBS within `bhyve` guests. The discussion also questioned `bhyve`'s overall reliability and testing thoroughness compared to its more established Linux counterpart, with inquiries into future development plans to address these gaps.