WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't

To: Thomas Goirand <thomas@xxxxxxxxxx>
Subject: Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Mon, 12 Apr 2010 12:34:01 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 12 Apr 2010 12:34:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BC19B2A.3040501@xxxxxxxxxx>
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: <20100408113422.GD4183@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20100408133820.GA29832@xxxxxxxxxxxxxxxxxxx> <20100408221953.GG4183@xxxxxxxxxxxxxxxxxxxxxxxxxx> <4BBE5DF2.6040707@xxxxxxxx> <20100409180016.GA14029@xxxxxxxxxxxxxxxxxxxxxxxxxx> <4BBF7004.8000707@xxxxxxxx> <20100410221349.GM4183@xxxxxxxxxxxxxxxxxxxxxxxxxx> <4BC1013D.2020003@xxxxxxxx> <4BC19B2A.3040501@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.4
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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>