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.
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.
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
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.
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.
A VM in a container actually
What will they thing of next? A container in a VM?
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.
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
You’re probably thinking of LXCs, which are containers not virtual machines
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