← All stories
● Covered by 1 source · 1 reportMedium impact1 neutral

Live Migration for bhyve Guests on FreeBSD 15.1 Reaches First Working State

🔄 Updated 8d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Live migration for bhyve guests on FreeBSD 15.1 is now functional.
  • Running amd64 guests can migrate between hosts over TCP.
  • Implementation uses dirty-page tracking and a new migration protocol.
  • Enables host maintenance and load balancing for virtualized environments.

Initial Implementation of Live Migration

A first working state for live migration of bhyve guests on FreeBSD 15.1 has been achieved. This allows a running amd64 guest to be moved between two hosts over TCP while continuing to operate, pausing only for the final stop-and-copy phase. The work integrates with bhyve's experimental snapshot support and adds dirty-page tracking within the vmm kernel module, alongside a new migration protocol in bhyve and bhyvectl.

Significance for Virtualization

Live migration is a core component for enterprise virtualization, facilitating host maintenance, hardware replacement, load balancing, and failure-domain management with reduced workload disruption. This functionality is also critical for the Sylve project, which aims to provide a Proxmox-like virtualization solution for FreeBSD, and for BoxyBSD, which offers free BSD-based VPS instances. Without live migration, routine host work can necessitate guest outages, making this development a key enabler for these platforms.

Technical Approach

The current implementation begins with a pre-copy phase, sending populated guest memory. It then repeatedly identifies and sends only the pages that have changed since the previous scan. Once the remaining dirty pages meet the configured downtime target, stop shrinking, or reach the round limit, bhyve pauses the guest and its devices. The final dirty pages and the existing snapshot state for vCPUs, kernel state, and emulated devices are then transmitted.

Migration Process

The destination host validates the VM geometry, receives and restores the memory and state, and signals readiness. The source then sends a 'GO' command, which acts as the commit point for the migration. Prior to this 'GO' command, a failed migration can be handled without data loss.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Live migration for bhyve guests on FreeBSD 15.1 is now in a first working state, allowing running amd64 guests to move between hosts over TCP with minimal interruption. This development builds on bhyve's experimental snapshot support and introduces dirty-page tracking in the vmm kernel module, along with a migration protocol in bhyve and bhyvectl. This capability is important for enterprise virtualization, enabling host maintenance and load balancing with less disruption, and is central to projects like Sylve and BoxyBSD.