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] Test results on Unisys ES7000 64x 256gb using unstable c

To: "Carb, Brian A" <Brian.Carb@xxxxxxxxxx>
Subject: Re: [Xen-devel] Test results on Unisys ES7000 64x 256gb using unstable c/s 16693 on 3.2.0 Release Candidate
From: Bill Burns <bburns@xxxxxxxxxx>
Date: Tue, 15 Jan 2008 08:50:23 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 15 Jan 2008 05:51:02 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <089B0D75973E1241B941D0A9854F23FC0A6125EC@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <089B0D75973E1241B941D0A9854F23FC0A6125EC@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.12 (X11/20071018)
Carb, Brian A wrote:
> Test results on Unisys ES7000 64x 256gb using unstable c/s 16693 on
> 3.2.0 Release Candidate
>  
> HOST:
> Unisys ES7000/one, x86_64, 64 processors, 256gb memory
> unstable changeset 16693 compiled with max_phys_cpus=64 and booted with
> dom0_mem=4096M, numa=on, and xenheap_megabytes=64
> from http://xenbits.xensource.com/staging/xen-unstable.hg pulled on
> 20080108:
>  

<snip>

We have noticed problems with dom0 initialization when not
limiting the memory for dom0 when we reach 112GB. This is using
3.1.2 and also appears in 3.1.3 as it stood last week. Note that
3.1.0 had no such issue. The problem is definately a Hypervisor
change of some sort (as opposed to a dom0 kernel change).

Wondering if anyone else sees this? And while it makes a lot
of sense to limit dom0 memory we have not in the past. And it's
somewhat problematic to know what to limit it too. We are in
the process of trying to determine what change set introduced
this regression.

Thanks,
 Bill

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