FreeBSD bhyve Live Migration: Moving VMs Between Hosts
Comments on “FreeBSD bhyve Live Migration: Moving VMs Between Hosts”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
A developer-published WIP RFC by gyptazy describes a first working live-migration implementation for amd64 bhyve guests on FreeBSD 15.1, moving running VMs over TCP with only a final stop-and-copy pause.
Why it ranked
No. 23 of 123 with a score of 0.61. The panel rated it highest on new information (0.95) and technical depth (0.79), lowest on audience breadth (0.42). Placed No. 23, No. 58 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- A substantive, technically detailed WIP RFC on bhyve live migration with dirty-page tracking and a clear blocker list; narrow audience (virtualization and FreeBSD users), no prior coverage, moderate significance and practical relevance.
- AI judgeJudge 3gpt-5.6-luna
- A technically detailed WIP implementation explains protocol, dirty-page tracking, failure handling, measurements, and concrete blockers. It is highly relevant to FreeBSD virtualization and infrastructure, though its audience is narrower than mainstream cloud engineering.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.61total under rubric v2.3
- Significance0.58
- Reader interest0.72
- Audience breadth0.42
- Practical relevance0.63
- Substantiated0.74
- Technical depth0.79
- New information0.95
- Counts against: Promotional0.13
- Counts against: Overclaim0.13
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.51 | 0.62 | 0.62 | 0.58 | 0.12 | +0.24 | +0.140 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.57 | 0.78 | 0.82 | 0.72 | 0.25 | +0.26 | +0.188 |
| Audience breadthHow many people who build technology does it concern? | 0.38 | 0.50 | 0.38 | 0.42 | 0.12 | +0.13 | +0.055 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.56 | 0.60 | 0.72 | 0.63 | 0.15 | +0.22 | +0.138 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.81 | 0.60 | 0.82 | 0.74 | 0.22 | +0.05 | +0.037 |
| Technical depthHow technically substantive is it? | 0.82 | 0.72 | 0.84 | 0.79 | 0.12 | +0.05 | +0.040 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.93 | 0.93 | 0.98 | 0.95 | 0.05 | +0.05 | +0.047 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.08 | 0.20 | 0.12 | 0.13 | 0.12 | −0.19 | −0.025 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.15 | 0.20 | 0.03 | 0.13 | 0.17 | −0.11 | −0.014 |
| Sum of contributions | +0.605 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.605 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-14/23/"><img src="https://rubric.hrih.si/badge/2026-11-14/23.svg" alt="Ranked #23 on Rubric, 14 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 6 no source given · 2 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Couldn’t checkGeneralization
A running amd64 bhyve guest can move between two hosts over TCP on FreeBSD 15.1 while continuing to run, paused only for the final stop-and-copy phase.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “A running amd64 guest can move between two hosts over TCP while continuing to run; it is paused only for the final stop-and-copy phase”
The source says No passage could be compared.
Source cited by the article: github.com/gyptazy/freebsd-bhyve-live-migration
Couldn’t checkVersion
The implementation builds on bhyve's experimental snapshot support and adds dirty-page tracking in the vmm kernel module plus a migration protocol in bhyve and bhyvectl.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “The work builds on bhyve's experimental snapshot support and adds dirty-page tracking in the vmm kernel module together with a migration protocol in bhyve and bhyvectl”
The source says No passage could be compared.
Source cited by the article: github.com/gyptazy/freebsd-bhyve-live-migration
No source givenNumber
For a slowly dirtying 512 MiB guest, observed downtime during live migration has been roughly 138–171 ms.
The article gives no link or citation for it.
The article says “For a slowly dirtying 512 MiB guest, observed downtime has been roughly 138–171 ms”
The source says No source to compare with.
No source givenGeneralization
In the two-host test environment, repeated live migrations, memory-rewrite workloads, and fsync-heavy disk workloads have completed successfully.
The article gives no link or citation for it.
The article says “repeated live migrations, memory-rewrite workloads, and fsync-heavy disk workloads have completed successfully”
The source says No source to compare with.
No source givenCausal conclusion
A rapidly dirtying guest may not converge during pre-copy but still falls back to a correct stop-and-copy completion with a longer pause.
The article gives no link or citation for it.
The article says “A rapidly dirtying guest may not converge during pre-copy, but still falls back to a correct stop-and-copy completion with a longer pause”
The source says No source to compare with.
No source givenCausal conclusion
The destination does not start the guest unless it receives the GO commit message, and before GO a failed migration can resume the source guest.
The article gives no link or citation for it.
The article says “Before GO, a failed migration can resume the source guest. The destination does not start the guest if it does not receive that commit message”
The source says No source to compare with.
No source givenNumber
The published test bed has primarily exercised a one-vCPU guest.
The article gives no link or citation for it.
The article says “The published test bed has primarily exercised a one-vCPU guest”
The source says No source to compare with.
No source givenGeneralization
The current TCP transport has no authentication or encryption and uses a first-version native protocol.
The article gives no link or citation for it.
The article says “The current TCP transport has no authentication or encryption and uses a first-version native protocol”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 139 pts, front page
Recorded for context only, checked 15 Nov 2026, 20:44 UTC. It played no part in the ranking.