On 01/11/2018 08:45 AM, 'Tom Zander' via qubes-users wrote: > I understand that there is a memory-manager to balance the memory between VM > spaces. > Does anyone know if dom0 is being managed this way? > > Currently there is 4GB assigned to dom0, of which 1.3 GB is in use. > At the same time I have chromium getting out-of-memory errors in an AppVM. > I'd like to actually use that 2½GB that dom0 now claims but doesn't use, > anyone got ideas how? > > Thanks!
There is a memory balancing bug in the R4 pre-release: https://github.com/QubesOS/qubes-issues/issues/created_by/tasket A workaround is to restart the qubes-qmemman.service periodically (sometimes I need to do this every 5min or so). I have also restricted dom0's max memory to help the situation. The permanent setting for this is 'dom0_mem=max:' in /etc/default/grub, which propagates to /boot/grub2/grub.cfg on the lines beginning with 'multiboot /xen'. Its currently at 1800M on this system and can probably go lower. -- Chris Laprise, [email protected] https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/30ebe4fa-cc65-5d30-1dcc-74f23d6b8430%40posteo.net. For more options, visit https://groups.google.com/d/optout.
