Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upModify meminfo-writer to provide qmemman just one number - used memory #1312
Comments
marmarek
referenced this issue
Oct 9, 2015
Closed
qmemman prevents creation of VMs with large amounts of RAM #1136
marmarek
added this to the Release 3.1 milestone
Oct 9, 2015
marmarek
added
enhancement
C: core
P: major
labels
Oct 9, 2015
marmarek
modified the milestones:
Release 4.0,
Release 3.1
Feb 8, 2016
added a commit
that referenced
this issue
May 31, 2016
added a commit
to marmarek/qubes-linux-utils
that referenced
this issue
Sep 18, 2016
woju
closed this
in
woju/qubes-core-admin@a2d9b15
Sep 21, 2016
added a commit
to marmarek/qubes-linux-utils
that referenced
this issue
Feb 27, 2017
added a commit
to marmarek/qubes-linux-utils
that referenced
this issue
Apr 8, 2017
qubesos-bot
referenced this issue
in QubesOS/updates-status
Apr 9, 2017
Closed
linux-utils v4.0.0 (r4.0) #32
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
marmarek commentedOct 9, 2015
Currently meminfo-writer provide a bunch of statistics, which are parsed by qmemman in dom0 and then a single number - used memory. This calculation doesn't require any external knowledge - use only data retrieved from a single VM. So can be done inside of VM, which would simplify data sanitization in qmemman.
The number provided by meminfo-writer should include all in-VM overhead.
This will also ease adding support for qmemman to other systems later.