community

rust-vmm community content

Explore on GitHub Read Hacker News discussions

2Distinct people

2Mentions

0Explicit recommenders

618GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

rust-vmm community content

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year2 dated mentions

Observed mentions: 2020-02-18 20:47:06 UTC to 2023-04-10 07:53:55 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	1	1
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	0	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	0	0
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	1	1

What Hacker News says

2 sources

stacktrust·Apr 10, 2023

The original post deserves an award for tech writing, https://cohost.org/cathoderaydude/post/1228730-taking-the-de... > Windows gets itself all ready for sleep, tucks itself in, then tells the BIOS "too eepy! time for bed, S3~" but instead of the S3 reaching the BIOS, OSM intercepts that call. The OS has halted itself, and is waiting to be told that it's time to wake up, but OSM instead proceeds to alter the universe around it ... the OSM will move all the memory pointers around, then reverse the sleep process, causing the machine to instantly "wake" - from a sleep it never actually entered. > Windows thinks it's taking a nap, but it wakes up as someone else, leaves the house, and commits murders it has no memory of. In other words: Phoenix figured out how to turn the BIOS into a hypervisor. It's almost, almost beautiful, if it wasn't bot

Read the rest

h incredibly fragile and completely uncalled-for. But christ. Christ almighty, what a hack. One could come to tears over it. There is a software archaeology epilogue waiting to be written, based on artifact reverse engineering and a trail of public breadcrumbs: Hyperspace was acquired by HP. Hyperspace creator left HP and founded Bromium (acquired by HP in 2019). Bromium productized OSS Type-2 Xen (uXen microvisor), copy-on-write VMs in 150ms. Microsoft cloned Bromium vSentry as Defender - Application Guard. Bromium AX ships on HP biz laptops /w nested x86 virt for OS+UEFI virt. OSS Bareflank hypervisor = attempt at replicating AX (Windows-as-dom0). OSS Android 13 pKVM-for-Arm is closest OSS in spirit to Bromium AX. In other words, conceptual descendants of the Phoenix Hyperspace hack are shipping today on millions of Android and Windows systems. In 2018, https://github.com/rust-vmm/community#why-rust-vmm deduped CrosVM (Chromebooks) and Firecracker (public cloud) micro VMs on KVM. Industry needs an OSS Type-1 L0 hypervisor: https://twitter.com/stacktrust/status/1640145980833005568 Video with virtualization history of Xen (Type 1), uXen (Type 2) and Bromium/HP AX (Type1 L0 for nesting of Xen, KVM, VMware, Hyper-V): https://www.youtube.com/watch?v=bNVe2y34dnM) pKVM baby step towards dropping SMM/TrustZone: https://twitter.com/stacktrust/status/1595951965699473408

In Hell Never Ends on x86: The Hyperspace Story, Continued, Sort Of

steveklabnik·Feb 18, 2020

Firecracker is a very interesting project. It's covered in the paper, but the origins are the "crosvm" project at Google, which is used in ChromeOS. Firecracker started as a fork of crosvm, removed a bunch of code they didn't need, and of course adding their own. But rather than just fork, they've consolidated the shared parts into the "rust-vmm" project: https://github.com/rust-vmm/community > The rust-vmm project is organized as a shared effort, shared ownership open-source project that includes (so far) contributors from Alibaba, AWS, Cloud Base, Crowdstrike, Intel, Google, Red Hat as well as individual contributors. This has allowed other similar tech to grow, like https://github.com/cloud-hypervisor/cloud-hypervisor, which seems to be the Intel project mentioned in the above sentence.

In Firecracker: Lightweight Virtualization for Serverless Applications