Virtualized Redox: from Virtio-FS to Cloud Hypervisor, and beyond
Comments on “Virtualized Redox: from Virtio-FS to Cloud Hypervisor, and beyond”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
MJ Pooladkhay describes building a Virtio-FS driver for Redox OS, now merged into the base repository, and getting Redox to boot to a shell on Cloud Hypervisor.
Why it ranked
No. 23 of 46 with a score of 0.57. The panel rated it highest on technical depth (0.93) and new information (0.92), lowest on audience breadth (0.42). Placed No. 23, No. 40 by score alone: the fourth Infrastructure & DevOps story of the day (−0.020). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Detailed, well-substantiated engineering writeup on running Redox OS as a VM guest with Virtio-FS and Cloud Hypervisor; technically deep and novel, but niche in audience and not landmark-level significance.
- AI judgeJudge 3gpt-5.6-luna
- A detailed, technically grounded engineering report on porting Redox to Cloud Hypervisor, including Virtio-FS, interrupts, timers, boot, isolation, tests, and future hosting. Highly relevant to OS, virtualization, infrastructure, and security practitioners, though still niche and partly aspirational.
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.57total under rubric v2.3
- Significance0.48
- Reader interest0.71
- Audience breadth0.42
- Practical relevance0.54
- Substantiated0.85
- Technical depth0.93
- New information0.92
- Counts against: Promotional0.08
- Counts against: Overclaim0.18
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.50 | 0.35 | 0.58 | 0.48 | 0.23 | +0.24 | +0.114 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.65 | 0.70 | 0.78 | 0.71 | 0.13 | +0.26 | +0.185 |
| Audience breadthHow many people who build technology does it concern? | 0.48 | 0.40 | 0.38 | 0.42 | 0.10 | +0.13 | +0.055 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.59 | 0.40 | 0.62 | 0.54 | 0.22 | +0.22 | +0.118 |
| 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.90 | 0.80 | 0.86 | 0.85 | 0.10 | +0.05 | +0.043 |
| Technical depthHow technically substantive is it? | 0.97 | 0.90 | 0.93 | 0.93 | 0.07 | +0.05 | +0.047 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.89 | 0.90 | 0.98 | 0.92 | 0.09 | +0.05 | +0.046 |
| 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.06 | 0.10 | 0.08 | 0.08 | 0.04 | −0.19 | −0.015 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.19 | 0.20 | 0.16 | 0.18 | 0.04 | −0.11 | −0.020 |
| Sum of contributions | +0.572 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.572 | ||||||
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-09/23/"><img src="https://rubric.hrih.si/badge/2026-11-09/23.svg" alt="Ranked #23 on Rubric, 9 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 2 no source given · 6 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 checkCausal conclusion
The Redox bootloader failed to leave UEFI because it passed a stale memory-map key to ExitBootServices.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “The bootloader failed to leave UEFI because it passed a stale memory-map key to ExitBootServices”
The source says No passage could be compared.
Source cited by the article: gitlab.redox-os.org/redox-os/bootloader/-/merge_requests/61
Couldn’t checkCausal conclusion
virtio-blk was matched as a transitional VirtIO device while Cloud Hypervisor only offers modern ones, so the Redox root disk never showed up.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “virtio-blk was matched as a transitional VirtIO device, while Cloud Hypervisor only offers modern (non-transitional) ones, so the root disk never showed up”
The source says No passage could be compared.
Source cited by the article: gitlab.redox-os.org/redox-os/base/-/merge_requests/422
Couldn’t checkCausal conclusion
The Redox login prompt did not accept keys because the serial input interrupt was aimed at a nonexistent 8259 controller; legacy interrupts are now routed through the I/O APIC.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Legacy interrupts are now routed through the I/O APIC”
The source says No passage could be compared.
Source cited by the article: gitlab.redox-os.org/redox-os/kernel/-/merge_requests/762
No source givenCausal conclusion
The only caller of timeout::trigger in the Redox kernel was the PIT interrupt handler, which never ran on Cloud Hypervisor because it has neither a PIT nor an HPET.
The article gives no link or citation for it.
The article says “the only caller of timeout::trigger was the PIT interrupt handler (on QEMU, the HPET drives the same interrupt line). Cloud Hypervisor has neither a PIT nor an HPET”
The source says No source to compare with.
Couldn’t checkCausal conclusion
When there is no HPET, each CPU now arms its own local APIC timer in TSC-deadline mode to post expired timeouts and drive the scheduler tick, making Redox preemptive again and letting ping -c 4 send all four packets.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “When there is no HPET, each CPU now arms its own local APIC timer in TSC-deadline mode”
The source says No passage could be compared.
Source cited by the article: gitlab.redox-os.org/redox-os/kernel/-/merge_requests/762
Couldn’t checkCausal conclusion
Cloud Hypervisor does not power off on the classic PM1 control register write that Redox's acpid uses; it is a hardware-reduced ACPI platform where shutdown is a write to the sleep control register.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “it writes the classic PM1 control register, and Cloud Hypervisor doesn’t power off on that”
The source says No passage could be compared.
Source cited by the article: uefi.org/specs/ACPI/6.5/04_ACPI_Hardware_Specification.html
No source givenGeneralization
Virtio-FS needs the virtiofsd daemon on the host, the same mechanism Kata Containers uses to give its VMs their files.
The article gives no link or citation for it.
The article says “It’s the same mechanism Kata Containers uses to give its VMs their files”
The source says No source to compare with.
Couldn’t checkGeneralization
Regular public cloud VMs and Firecracker do not offer Virtio-FS, and Redox already boots on Google Cloud with an ordinary attached disk.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Regular public cloud VMs and Firecracker don’t offer Virtio-FS, so there the persistent part goes on an ordinary attached disk instead, which already works”
The source says No passage could be compared.
Source cited by the article: redox-os.org/news/this-month-260930
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN —
Recorded for context only, checked 9 Nov 2026, 05:46 UTC. It played no part in the ranking.