I recently found out about a Linux Distro named Q4OS and I wanted to test out their claim that it only requires 256 MB of ram when using the trinity desktop environment. However, when I used the live cd in virt-manager with 256 MB or ram, it just kernel panicked at boot. So I then tried it with 512 MB of ram. In addition to some issues that are not present when you are using at least 1 GB of ram, such as “sudo apt update” causing the entire VM to become unresponsive, I noticed that it seemed to actually use anywhere between 290 MB to 370 MB of ram when the only thing running was the process viewer (which is htop).

Obviously, this is still very low for a modern Linux distro but I was wondering how accurate VMs are for testing ram usage.

And, yes I know that it would be pretty much useless on a PC that only had 256 MB of ram even if it did work. I’m actually checking the ram usage because there is a possibility that I may be using a very old computer of mine that only has 1 GB of ram at some point in the future. So I’m just testing it and eventually other distros out to to see which one I’m going to end up using (assuming I do actually end up even using that computer).

Edit: I just tried the 32-bit version in virt-manager and htop stated it was only using 232 MB of ram, which means that their claim was right and that I might have been using the wrong version. Also, because someone mentioned that live cds can use more ram, I will try actually installing the 64-bit version but I’ll have to do that tomorrow because I’m about to go to bed.

  • BCsven@lemmy.ca
    link
    fedilink
    arrow-up
    1
    ·
    5 months ago

    On a somewhat unrelated note: I have an old Iomega arm board running an old version of Debian and OpenMediaVault, it only has 256 MB RAM, and only uses about 30% of that while streaming DLNA audio. Linux can be super minimal

  • allywilson@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    5 months ago

    To answer the question of discrepancies, yes. There are actually different types of virtualisation techniques that offer different levels of interaction between the VM and the hardware (negating the use of additional emulation and processing, etc.). Look up paravirtualisation.