Re:Unfashionably secure: why we use isolated VMs
by yjftsjthsd-h on Thursday July 25, 2024 @03:38PM
(#41072536)
It would be interesting to see a microvm (kata/firecracker/etc.) version of vagrant. And open source, of course. I can't see any technical reason why it would be particularly difficult.
[ Parent
| on HN ]
Re:Unfashionably secure: why we use isolated VMs
by mountainriver on Thursday July 25, 2024 @07:44PM
(#41074620)
Oh they exist! Several of them in fact, they have never picked up a ton of steam though
Re:Unfashionably secure: why we use isolated VMs
by packetlost on Thursday July 25, 2024 @09:16PM
(#41075081)
I don't think they're that valuable tbh. Outside of cases where you're running completely untrusted code or emulating a different architecture, there's no strong reason to pick any VM over one of the several container paradigms.
Re:Unfashionably secure: why we use isolated VMs
by yjftsjthsd-h on Thursday July 25, 2024 @10:57PM
(#41075464)
One more usecase - which I admit is niche - is that I want a way to run multiple OSs as transparently as possible. A microvm that boots freebsd in less than a second and that acts almost like a native container would be excellent for certain development work.
Edit: Actually it's not just cross-OS work in the freebsd/linux sense; it would also be nice for doing kernel dev work. Edit my linux kernel module, compile, and then spawn a VM that boots and starts running tests in seconds.
Re:Unfashionably secure: why we use isolated VMs
by packetlost on Friday July 26, 2024 @09:57AM
(#41078721)
Yeah, there are definitely still cases, but they're when you specifically want/need a different kernel, which as you said are rather niche.