This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] RE:2Gb Memory lost in - 50G memory, maxmem=50G

To: MaoXiaoyun <tinnycloud@xxxxxxxxxxx>
Subject: Re: [Xen-devel] RE:2Gb Memory lost in - 50G memory, maxmem=50G, 2G used for pagetable, clamping (max:5G) is not helping.
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 31 May 2011 10:44:21 -0400
Cc: jeremy@xxxxxxxx, xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 31 May 2011 07:55:29 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BLU157-w405ED0B907334E184E4722DA7A0@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <SNT0-MC4-F34MpzkUY6002755b8@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <BLU157-w147E2A05A8AC5335C0A85BDA8F0@xxxxxxx> <BLU157-w44D25547BD8C553EF8D6B8DA8E0@xxxxxxx> <BLU157-w46754A04E8A3A21400AA1BDA8E0@xxxxxxx> <BLU157-w1E33BE64D768511906790DA8E0@xxxxxxx> <20110519144242.GC9854@xxxxxxxxxxxx> <BLU157-w27A65EFF61E3E94BD5544EDA8E0@xxxxxxx> <20110519161656.GA12889@xxxxxxxxxxxx> <BLU157-w44733E151C7AE97BF6D3B4DA740@xxxxxxx> <BLU157-w405ED0B907334E184E4722DA7A0@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
On Tue, May 31, 2011 at 04:33:52PM +0800, MaoXiaoyun wrote:
> Hi Konrad;
>       I realized that in 32.36 kernel dom0 can balloon up to use whole memory 
> address, in my case it is 48G. But it consumes 845M memory 
> for sparse memory to manage them, Well, my dom0 doesn't need so big flexable, 
>  and I learnt that use "mem=" option in grub can limit 
> dom0 memory, I think it works for me now.  

HA! That does it too.
> Any comments?

> title Red Hat Enterprise Linux Server (
>         root (hd0,0)
>         kernel /xen-4.0.1.gz  iommu=off x2apic=off console=com1,vga 
> com1=115200,8n1 noreboot dom0_mem=6144M dom0_max_vcpus=4 dom0_vcpus_pin 
> cpuidle=0 cpufreq=none 
>         module /vmlinuz- ro root=LABEL=/ hda=noprobe console=hvc0 
> mem=8192M
>         module /initrd-

That is a good work-around. Still need to fix the bug in the E820 setup code to 
dom0_mem=max: parameter under advisment.

Xen-devel mailing list