From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Wright <anthony@overnetdata.com>
Subject: Re: 5x dom0 memory increase from Xen/Linux 3.4/2.6.18
	to	4.1/3.0.0
Date: Wed, 22 Jun 2011 15:22:30 +0100
Message-ID: <4E01FAA6.8030304@overnetdata.com>
References: <20110616145611.GC6108@dumpdata.com>
	<25543076.8.1308324671857.JavaMail.root@zimbra.overnetdata.com>
	<20110620124521.GC2973@dumpdata.com>
	<4E01EAF7.9030900@overnetdata.com>
	<20110622133243.GA8722@dumpdata.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20110622133243.GA8722@dumpdata.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 22/06/2011 14:32, Konrad Rzeszutek Wilk wrote:
> On Wed, Jun 22, 2011 at 02:15:35PM +0100, Anthony Wright wrote:
>> Maybe I'm misreading the output, but I couldn't see any numbers that
>> look like memory being assigned. I've attached the dmesg output. Do I
>> need to enable a CONFIG variable to get the output I need or am I
>> missing something.
> The memblock=debug should give you some idea of what is Reserved. The
> Reserved includes memory that is allocated by boot-time services (P2M,
> pagetables, NUMA) and by real reservations (for example ACPI space).
> Using the 'memblock=debug' can give you an idea of what services are
> reserving the most. Then we can narrow down who or what is eating the gobs
> of memory.
>
> see the 'Memory: ".. numbers. Also you might want to eliminate
> the balloon usage space algother by doing two things:
>
> Xen command line: dom0_mem=max:512MB
>
> Linux command line: mem=512MB
>
> That will effectivly remove any balloon space (so your Dom0 will _never_
> grow up).
The problem is I can't see any lines in the kernel dmesg output
(attached to previous email) that start "Memory: ", or anything else
that looks hopeful. Is there anything else I should add to the command
line, is there a kernel CONFIG option I should turn on or am I missing
something else?

thanks,

Anthony.