From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: linux kernel 2.6.37 Date: Tue, 25 Jan 2011 09:45:23 -0500 Message-ID: <20110125144523.GB7238@dumpdata.com> References: <4D384204020000260001866B@hibbing.edu> <1295554269.22720.6.camel@mobile> <20110120201937.GR2754@reaktio.net> <1295563321.22720.17.camel@mobile> <20110121153056.GA4698@dumpdata.com> <1295626578.32475.2.camel@mobile> <1295900343.2349.6.camel@mobile> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1295900343.2349.6.camel@mobile> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Vasiliy G Tolstov Cc: Don Brearley , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Mon, Jan 24, 2011 at 11:19:02PM +0300, Vasiliy G Tolstov wrote: > On Fri, 2011-01-21 at 19:16 +0300, Vasiliy G Tolstov wrote: > > On Fri, 2011-01-21 at 10:30 -0500, Konrad Rzeszutek Wilk wrote: > > > > > Do you see any messages during bootup about memory being returned? Look for > > > xen_release_chunk .. and pages freed ? > [snip] > > Hello. Konrad, do You have any progress about this issue? Try booting your kernel with 'debug loglevel=10 memblock=debug'. I know that at least 64MB is used for SWIOTLB (which you don't need - you can disable that since you are not doing any PCI passthrough), 6MB for kernel + kernel data. The "memblock=debug" will give you the details to figure out who else is eating the big swaths of memory. Is this also a problem if you boot the guest as HVM? What happens if you boot your PV guest without 'maxmem=4096' and .. oh, I think I know why this is happening = the kernel allocates pagetables as if you have 4GB of memory and that eats much of low memory. If you decrease the 'maxmem' you should see a smaller amount being used.