[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Test results on Unisys ES7000 64x 256gb using unstable c/s 16693 on 3.2.0 Release Candidate


  • To: Bill Burns <bburns@xxxxxxxxxx>, "Carb, Brian A" <Brian.Carb@xxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Tue, 15 Jan 2008 14:44:53 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 15 Jan 2008 06:46:06 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AchXhTAkboCR4cN4Edy5ZgAX8io7RQ==
  • Thread-topic: [Xen-devel] Test results on Unisys ES7000 64x 256gb using unstable c/s 16693 on 3.2.0 Release Candidate

On 15/1/08 13:50, "Bill Burns" <bburns@xxxxxxxxxx> wrote:

> 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.

Have you tried 3.2.0 release candidates?

I doubt any other developers are going to run into this as we're not
overwhelmed with 128GB+ systems.

 -- Keir



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.