Show HN: microvm – a minimalist machine type for QEMU inspired by Firecracker
1–10 of 22 posts
Re: Show HN: microvm – a minimalist machine type for QEMU inspired by Firecracker
#2What are the differences compare to Firecracker?
Re: Show HN: microvm – a minimalist machine type for QEMU inspired by Firecracker
#3Oh, nice: props for including precise, fully worked example commands to actually use this. This is so helpful in terms of onboarding and being able to actually get people to use a project:)
Re: Show HN: microvm – a minimalist machine type for QEMU inspired by Firecracker
#4What are the differences compare to Firecracker?
From the guest perspective, the differences are minimal. Even boot time of the guest (thinking about a custom-built minimalist Linux kernel here) is roughly the same.
On the host side, things are more interesting. Firecraker has a smaller TCB (Trusted Computing Base), is written in Rust, and is statically linked. On the other hand, QEMU provides more features (especially in the block layer, with more formats, network-based block devices, asynchronous I/O...), can be configured at build time to adapt it to a particular use case, and has a pretty good security record.
In the end, KVM userspace VMMs (Virtual Machine Monitors) are learning from each other, giving users more options to choose from. Everybody wins.
Re: Show HN: microvm – a minimalist machine type for QEMU inspired by Firecracker
#5What are the differences compare to Firecracker?
[deleted]
Re: Show HN: microvm – a minimalist machine type for QEMU inspired by Firecracker
#6Oh, nice: props for including precise, fully worked example commands to actually use this. This is so helpful in terms of onboarding and being able to actually get people to use a project:)
If I was an eccentric billionaire, I'd reward good documentation with an open source doc prize.
It's so difficult to impress upon some people just important documentation is. And when they do it, they half-ass it by copying stuff from source code and not adding any context.
Re: Show HN: microvm – a minimalist machine type for QEMU inspired by Firecracker
#7Firecracker requires KVM, but QEMU can be used with instruction emulation, correct? Does that make this potentially a little easier to develop with in certain environments?
Re: Show HN: microvm – a minimalist machine type for QEMU inspired by Firecracker
#8Firecracker requires KVM, but QEMU can be used with instruction emulation, correct? Does that make this potentially a little easier to develop with in certain environments?
That's correct. The initial versions of the microvm patch series did require KVM, but the one that got upstreamed does work with TCG [1], thanks to the QEMU's maintainers feedback.
That said, I'm not sure for which kind of use cases it would be useful to run it this way, as the performance won't be amazing. I find TCG acceleration mainly useful for debugging and foreign systems emulation.
Re: Show HN: microvm – a minimalist machine type for QEMU inspired by Firecracker
#9Firecracker requires KVM, but QEMU can be used with instruction emulation, correct? Does that make this potentially a little easier to develop with in certain environments?
I wonder if that's a security benefit, too... I would expect that KVM equals more attack surface, and direct to the host kernel at that. Now, weighing likelihood of exploiting KVM through qemu vs qemu through TCG (or whatever)... I'm not qualified to asses, and probably depends on your threat model. But it sure feels good if you can run qemu with no special privileges.
Re: Show HN: microvm – a minimalist machine type for QEMU inspired by Firecracker
#10What kind of workloads make sense for this runtime? DIYFaaS? Or small, isolated long-running processes?