From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages Date: Mon, 12 Apr 2010 12:34:01 -0700 Message-ID: <4BC375A9.1060904@goop.org> References: <20100408113422.GD4183@kepler.schwinge.homeip.net> <20100408133820.GA29832@phenom.dumpdata.com> <20100408221953.GG4183@kepler.schwinge.homeip.net> <4BBE5DF2.6040707@goop.org> <20100409180016.GA14029@kepler.schwinge.homeip.net> <4BBF7004.8000707@goop.org> <20100410221349.GM4183@kepler.schwinge.homeip.net> <4BC1013D.2020003@goop.org> <4BC19B2A.3040501@goirand.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4BC19B2A.3040501@goirand.fr> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Thomas Goirand Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 04/11/2010 02:49 AM, Thomas Goirand wrote: >> Excellent. >> > Could this be also the reason why I had very funky memory management > (eg: some RAM missing between "xm list" and "xm info")? > I don't think so. Before I added the "unused memory freeing" code, then you'd see memory assigned to a domain that the domain itself couldn't use, and so it was effectively wasted. With the memory-freeing in place, the "xm list" and the domain's internal view of memory should be basically the same. Either way, it shouldn't have any effect on the global memory accounting shown by xm info. J