Not being familiar with this area the page didn't help me understand the use case. This explanation of firecracker makes some sense though: "firecracker is purposefully minimal to present less possibility for configuration mishaps and importantly minimal attack surface (it's usually used to run untrusted workloads). Also full control by ReST-API makes it easy to orchestrate."
It's a very cool thing and through the magic of virtiofs I'm (almost) at a point at which I have a script that I can point at a directory with a Linux file system and boot it in a microVM in under a second.
It required quite a bit of trial and error because the components aren't very well documented and don't seem to be made for each other. I meant to publish something about it but never got around to it.
It'll likely be a lot of work to get going, but it might contain some valuable hints that I had to search for through mailing lists and reading the QEMU source.
I remember needing a semi-custom kernel (maybe) and (I think) the rust version of virtiofsd.
7 comments
[ 3.2 ms ] story [ 29.9 ms ] threadhttps://stackoverflow.com/questions/74512158/what-makes-the-...
We replaced Firecracker with QEMU - https://news.ycombinator.com/item?id=36666782 - July 2023 (137 comments)
Previously:
Show HN: microvm – a minimalist machine type for QEMU inspired by Firecracker - https://news.ycombinator.com/item?id=21461701 - Nov 2019 (20 comments)
It required quite a bit of trial and error because the components aren't very well documented and don't seem to be made for each other. I meant to publish something about it but never got around to it.
It'll likely be a lot of work to get going, but it might contain some valuable hints that I had to search for through mailing lists and reading the QEMU source. I remember needing a semi-custom kernel (maybe) and (I think) the rust version of virtiofsd.