3 ms·
To make Firefox happy inside a VM it takes up about 2GB RAM. Dom0 eats up 1G RAM. sys-net, sys-firewall, sys-usb eats up another 1G RAM. My collegue actually r
by isodude 5y ago
To make Firefox happy inside a VM it takes up about 2GB RAM.
Dom0 eats up 1G RAM. sys-net, sys-firewall, sys-usb eats up another 1G RAM.
My collegue actually runs on 16G, but he has to consider memory when starting a VM, but it's doable.
You can run on 8G, but it wouldn't be a good daily driver. But maybe if you have a very specific purpose?
24G+ is comfortable. I'm currently at 48G and have 43G "mapped" to VMs. It's very easy to use a lot of RAM!
- fsflover 5y agoYou can drastically decrease the memory footprint if you use minimal templates: https://www.qubes-os.org/doc/templates/minimal https://www.qubes-os.org/doc/templates/minimal. But even with normal templates, one can run several VMs, and it's much more secure (and even convenient) than an ordinary OS.
- lapinot 5y agosys-net, sys-firewall and other administrative vms should slowly migrate to unikernels instead of running linux, which should help with ram usage. The mirage.io project seems to build a couple qubes vms, for example https://github.com/mirage/qubes-mirage-firewall https://github.com/mirage/qubes-mirage-firewall is a firewall which they indicate to give 64Mb of ram. edit: maybe i'm being a bit optimistic for sys-net, which is the vm hosting the driver for the network card: these drivers are included in the linux tree and would need to be extracted and packaged into an unikernel. But for every non-driver vm it "should be easy" to get an unikernel implementation (drivers for paravirtual devices are easy to write).