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] 5x dom0 memory increase from Xen/Linux 3.4/2.6.18 to 4.1

On Wed, Jun 22, 2011 at 03:22:30PM +0100, Anthony Wright wrote:
> 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

dmesg | grep Memory: ?

Xen-devel mailing list