![Thumbnail of Why We Replaced Firecracker with QEMU | Hocus Blog](https://hocus.dev/blog/img/hocus-logo-with-text.png)
Why We Replaced Firecracker with QEMU | Hocus Blog
![Thumbnail of Why We Replaced Firecracker with QEMU | Hocus Blog](https://hocus.dev/blog/img/hocus-logo-with-text.png)
Here are the two most significant features Firecracker lacks:
- Dynamic memory management - Firecracker's RAM footprint starts low, but once a workload inside allocates RAM, Firecracker will never return it to the host system. After running several workloads inside, you end up with an idling VM that consumes 32 GB of RAM on the host, even though it do