From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: xen does not see more than 173800500k of memory
Date: Thu, 23 Aug 2007 15:27:14 +0100
Message-ID: <C2F357D2.14826%keir@xensource.com>
References: <46CD54BB.76E4.0078.0@novell.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <46CD54BB.76E4.0078.0@novell.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/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/cgi-bin/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: Jan Beulich <jbeulich@novell.com>, Susan Krysan <KRYSANS@unisys.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

This should be easily fixed by properly applying
domain_clamp_alloc_bitsize() in __alloc_domheap_pages(). Why is it only
applied when the bitsize is explicitly specified by the caller?

I think that's the only thing to fix to allow the 166GB boot-time
restriction to be lifted, but am I missing something, Jan?

 -- Keir

On 23/8/07 08:34, "Jan Beulich" <jbeulich@novell.com> wrote:

> This seems to correspond to the truncation at 166Gb for 32on64 support (see
> xen/arch/x86/e820.c:machine_specific_memory_setup()). There used to be
> a command line options to disallow creation of compat mode guests (thereby
> allowing all memory to be used), but that option went away with fairly recent
> changes.
> 
> Jan
> 
>>>> "Krysan, Susan" <KRYSANS@unisys.com> 23.08.07 00:33 >>>
> Our test server (Unisys ES7000) has recently been upgraded with more
> processors and more memory, so I am testing x86_64 xen with 64 cpus and
> 192gb.  I compiled xen with max_phys_cpus=64 and debug=y.  xen sees the
> 64 cpus, but only sees 173800500k of the 192gb.  I booted dom0 with
> 2048M and numa=on.  I get the same result when I configure the server to
> have 176gb (xen still sees only 173800500k). Booting without numa=on
> makes no difference.
> 
>  
> 
> xentop - 14:48:42   Xen 3.0-unstable
> 
> 1 domains: 1 running, 0 blocked, 0 paused, 0 crashed, 0 dying, 0
> shutdown
> 
> Mem: 173800500k total, 4324748k used, 169475752k free    CPUs: 64 @
> 3400MHz
> 
>       NAME  STATE   CPU(sec) CPU(%)     MEM(k) MEM(%)  MAXMEM(k)
> MAXMEM(%) VCPUS
> 
>  NETS NETTX(k) NETRX(k) VBDS   VBD_OO   VBD_RD   VBD_WR SSID
> 
>   Domain-0 -----r         95    0.0    2097152    1.2   no limit
> n/a    32
> 
>     0        0        0    0        0        0        0    0
> 
>  
> 
> When I configure the server with 160gb or less, xen sees all of the
> memory. 
> 
>  
> 
> Also, when I boot with the SLES kernel, SLES can see the all of the
> memory.
> 
>  
> 
> I assume there is not a memory limit on xen.  I would greatly appreciate
> any help to resolve this problem.
> 
>  
> 
> Thanks,
> 
> Sue Krysan
> 
> Linux Systems Group
> 
> Unisys Corporation
> 
>  
> 
>  
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel