Re:Run isolated sandboxes with full lifecycle control: AWS i...
by binsquare on Friday June 26, 2026 @03:38PM
(#48691024)
I designed my take to basically eliminate the concept of vm being a rigid box of cpu/memory with CPU oversubscription and virtio-ballooning on memory + sparse ext4.
That way it can be elastic in CPU, memory and somewhat disk.
How far are you on your take?
I am quite sure I'm not the only person working on post-firecracker KVM.