|
|
|
|
|
|
by isabellat
1506 days ago
|
|
|
Really excited about this and rust-vmm which allows you to build custom Virtual Machine Monitors. The problem with a solution like Firecracker, and why they are able to get such fast startup times and a small memory footprint is that they selected a subset of features to expose. This limits the capabilities of the running container, which is of course the point. But it is not general purpose enough for all workloads. For instance, I want to use Firecracker but require host file system sharing. Rust-vmm looks like it is trying to solve this problem by providing a collection of rust crates that allow users build their own VMM with the features they need. It's build-a-bear for VMMs :) |
|
|
Yeah!
Nearly everybody says they want a simple and minimal solution in this space, but everybody means different things when they say that. For example, in Lambda we do everything at the block level, and intentionally don't want to share filesystems (one reason is that it exposes the host kernel's complex FS code to the guest). But you want filesystems, and that's cool.
Instead of having a box that does everything, with the associated size and attack surface, rust-vmm moves that feature binding to build time. It's slightly less convenient, but much more powerful.
(I'm the guy in the video on the linked page, but this is just my opinion, nothing official)