Extra security and full isolation with its own kernel, so you can load kerne modules and such.
Also can run Windows in a VM when needed, or MacOS.
Comment on Selfhosting Sunday - What's up to date, selfhosters?
azron@lemmy.ml 10 months agoI find VMs to BR unbearably sloe compared to a container. They just feel so heavy. I get the extra security layer, is that really why people are doing it or is there some other reason?
MangoPenguin@lemmy.blahaj.zone 10 months ago azron@lemmy.ml 10 months ago
VMs are not just as fast as containers.
- MangoPenguin@lemmy.blahaj.zone 10 months ago
I didn’t say that, I said almost! Generally disk IO is where VMs fall short on performance vs a container.
frongt@lemmy.zip 10 months ago
Not everything runs in a container.
deadcade@lemmy.deadca.de 10 months ago
Being able to choose the OS and kernel is also important. I would not want my hypervisor machine to load GPU kernel modules, especially not on an older LTS kernel (which often don’t support the latest hardware). Passing the GPU to a VM ensures stability of the host machine, with the flexibility to choose whatever kernel I need for specific hardware. This alongside running entirely different OSes (like *BSD, Windows :(, etc) is pretty useful for some services.
McMonster@programming.dev 10 months ago Portability, isolation, the ability to run pretty much anything inside. They do consume more resources, but if they’re that much slower then there’s probably something wrong in your setup.
non_burglar@lemmy.world 10 months ago
The easy ui is good for those who aren’t living in the terminal all the time.
I used proxmox for nearly 8 years before switching to only containers. It was fine.