maxmem setting doesn't work for dispVM

[marmarek]

Reported by cjlee112 on 11 Jun 2013 14:38 UTC
On 10.06.2013 01:36, Christopher Lee wrote:

Following Marek's instructions, I set

qvm-prefs -s fedora-18-x64-dvm maxmem 3072
qvm-create-default-dvm --default-template --default-script

However, I later noticed that a running dispVM memory allocation increased
over 4 GB (and it kernel-panicked as a result, due to a separate bug which
Marek says is known). So clearly the maxmem setting did not work.

On 11.06.2013 07:43, Christopher Lee wrote:

OK, the problem is recurring right now in this dispVM I'm using to write to
you:

xenstore-read still shows static-max as 3145728

but qvm-ls -m shows disp1 mem = 3324 MB

qmemman.log shows disp1 (dom id 7) messages like:

dom 7 act/pref 3772116992 387432448.0
xenfree= 68792320 balance req: [('7', 3486158456), ...
mem-set domain 7 to 3486158456

Migrated-From: https://wiki.qubes-os.org/ticket/736

[marmarek]

Comment by joanna on 1 Aug 2013 12:33 UTC
Seems like a #259 dup.

[marmarek]

Comment by joanna on 1 Aug 2013 12:33 UTC
Seems like a #259 dup.

[marmarek]

Comment by marmarek on 22 Oct 2013 00:03 UTC
No, it isn't duplicate.

[marmarek]

Comment by marmarek on 22 Oct 2013 00:03 UTC
No, it isn't duplicate.

[marmarek]

Comment by marmarek on 22 Oct 2013 00:06 UTC
http://git.qubes-os.org/?p=marmarek/core-admin.git;a=commit;h=71960d83cc08a7a19afcca0f369b58ef47999c13

Looks like maxmem handling in qmemman have never worked before...

[marmarek]

Comment by marmarek on 22 Oct 2013 00:06 UTC
http://git.qubes-os.org/?p=marmarek/core-admin.git;a=commit;h=71960d83cc08a7a19afcca0f369b58ef47999c13

Looks like maxmem handling in qmemman have never worked before...