Ram Limit

59 views
Skip to first unread message

Thomas Druilhe

unread,
May 15, 2018, 11:07:27 AM5/15/18
to qubes-users
Hi,

We are using Qube-os 3.2 and sometimes we got a problem with RAM usage.
We set up minimum limit at 400Mo but sometimes RAM drop to 320 Mo causing crash of the application.

How the amount of RAM can be under the limit fixed in the settings of the VM ?

Best Regards

Tai...@gmx.com

unread,
May 15, 2018, 6:04:14 PM5/15/18
to qubes...@googlegroups.com
On 05/15/2018 11:07 AM, Thomas Druilhe wrote:

> Hi,
>
> We are using Qube-os 3.2 and sometimes we got a problem with RAM usage.
Corporate user?
> We set up minimum limit at 400Mo but sometimes RAM drop to 320 Mo causing crash of the application.
>
> How the amount of RAM can be under the limit fixed in the settings of the VM ?
Well you can have as much as you please via the pre-allocate option
disabling memory scaling.

If you are using memory balancing the issue is probably not having
enough on the host thus you are memory starved.

I suggest pre-allocation for critical applications VMs, such as if one
was using xen (not qubes ofc) for a domain controller, DNS, etc.
0xDF372A17.asc

awokd

unread,
May 15, 2018, 11:02:19 PM5/15/18
to Tai...@gmx.com, qubes...@googlegroups.com
I think Thomas is saying he's setting a minimum of 400MB but sees the VM
dropping to 320MB and crashing. Your solution of setting a fixed memory
size and disabling memory balancing on the VM should also work in that
case!


Drew White

unread,
May 16, 2018, 1:52:08 AM5/16/18
to qubes-users

I have a minimum of 256 MB.
My NetVM and ProxyVM have 256 MB RAM assigned.

Hard assignment.
I generally have everything hard assigned if they are for low RAM usage.
High usage I set for 2/3 GB RAM.
The rest I have set as min 400 and max 4000.
I have never experienced the issue you are referring to.
Unless you are using Firefox or similar because that can happen because FF is badly programmed.
I would also recommend not using the Qubes Manager, as it is resource hungry.

I have Dom0 set at 2048 MB RAM.
If I use Qubes Manager I need to have an extra 1 GB of RAM available AT LEAST.

So I would recommend you look at your global settings and the setting of your computer too.

Setting manual sizes is good, but for a few, instead of 4000 MB, set it to 4 GB (4096 MB)
Try and always keep it to the right multiples.
This will help in many things.
1,2,4,8,16,32,64,128,256,512,... etc..
If you keep everything in multiples of 256 for RAM, then I find everything works smoothly with Dom0 using 2048 MB RAM.

I can have it as 1024, but then the virtual system has no turn around space in Dom0. So I would recommend 2048 MB RAM for Dom0 as a minimum. (Until a better, less resource hungry system is used for Dom0, like Slackware [personal opinion])

The Minimum Allocation for RAM is only the minimum for what you assign in the manager. Not the minimum that things will use or allocate to use.


Tai...@gmx.com

unread,
May 18, 2018, 11:50:24 PM5/18/18
to qubes...@googlegroups.com
On 05/15/2018 11:01 PM, awokd wrote:

> I think Thomas is saying he's setting a minimum of 400MB but sees the VM
> dropping to 320MB and crashing. Your solution of setting a fixed memory
> size and disabling memory balancing on the VM should also work in that
> case!

Oh no I don't mean that :[ such a thing should only be done for critical
applications VM's not all of them, but I had the same issue which was
caused by some kind of memory leak now I must restart every so often or
else I am only able to run a dwindling amount of appVM's on qubes 3.2
0xDF372A17.asc
Reply all
Reply to author
Forward
0 new messages