Why We Replaced Firecracker with QEMU | Hocus Blog
hocus.dev · 894 words · saved by 1 readers
Firecracker is not the best choice for all kinds of workloads.
Firecracker, the microVM hypervisor, is renowned for being lightweight, fast, and secure. It's excellent for running short-lived workloads, which is why it's the backbone of AWS Lambda. Our initial prototype for Hocus, a self-hosted alternative to Gitpod and GitHub Codespaces, utilized Firecracker. However, after weeks of testing, we decided to entirely replace it with QEMU. A little-known fact about Firecracker is its lack of support for many modern hypervisor features, such as dynamic RAM management, which is vital for long-lived workloads. In this post, I will explain why Firecracker might
saved by
related reading
- firecracker/docs/design.md at main · firecracker-microvm/firecrackergithub.com
- nsdi20-paper-agache.pdfusenix.org
- NYSRGnotes.ekzhang.com
- On-demand Container Loading in AWS Lambdaarxiv.org
- How we got microVMs booting in under a seconddepot.dev
- 100R - weathering software winter100r.ca
- Cloud Computing without Containers | The Cloudflare Blogblog.cloudflare.com
- What is AWS Lambda? - AWS Lambdadocs.aws.amazon.com
- Hot Chips 2026: Applying High Bandwidth Flash (HBF)chipsandcheese.com
- From bare metal to a 70B model: infrastructure set-up and scripts - Imbueimbue.com
- "VMs won't contain cyber-capable agents"blog.trailofbits.com
- Linux in a Pixel Shader - A RISC-V Emulator for VRChatblog.pimaker.at