this post was submitted on 02 Sep 2025
66 points (93.4% liked)

Linux

9406 readers
270 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] F04118F@feddit.nl 3 points 2 weeks ago (2 children)

Virtualbox is VMs. This is containers.

Containers are better, especially for a desktop: they are smaller, faster in every sense, and don't permanently hog a fixed part of the resources, instead scaling dynamically, just like any other process on the host.

[–] boredsquirrel@slrpnk.net 17 points 2 weeks ago (1 children)
[–] Ulrich@feddit.org 1 points 1 week ago (1 children)

What will they thing of next? A container in a VM?

[–] boredsquirrel@slrpnk.net 2 points 1 week ago

Actually that is how ChromeOS does the Linux environment. They run a container image in a small performant VM and passthrough the windows with some fancy Wayland tool.

[–] Jenseitsjens@lemmy.world 4 points 2 weeks ago (1 children)

Nowadays you can also assign a dynamic amount of memory. I've only ever used this with Linux VMs on Proxmox though, but I'm pretty sure it works with Windows as well

[–] Jakeroxs@sh.itjust.works 2 points 2 weeks ago (1 children)

You're probably thinking of LXCs, which are containers not virtual machines

[–] Jenseitsjens@lemmy.world 8 points 2 weeks ago

No I'm talking about VMs. It's the baloon kernel driver which also works on Windows (though needs separate installation). It doesn't work quite like containers though. The hypervisor dynamically adds/removes memory to the VM depending on total memory usage of the hypervisor.

See https://pve02.northcode.ch:8006/pve-docs/chapter-qm.html#qm_memory