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


Re: [Xen-devel] Test results on Unisys ES7000 64x 256gb using unstablec/

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Test results on Unisys ES7000 64x 256gb using unstablec/s 16693 on 3.2.0 Release Candidate
From: Bill Burns <bburns@xxxxxxxxxx>
Date: Fri, 01 Feb 2008 07:40:25 -0500
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Carb, Brian A" <Brian.Carb@xxxxxxxxxx>
Delivery-date: Fri, 01 Feb 2008 04:40:59 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3C88A9D.13266%Keir.Fraser@xxxxxxxxxxxx>
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: <C3C88A9D.13266%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20071129)
Keir Fraser wrote:
> On 31/1/08 18:12, "Bill Burns" <bburns@xxxxxxxxxx> wrote:
>> I instrumented read_pmtimer_count and it does get called a couple
>> of times during startup and it returns an increasing value. I made
>> no attempt to determine if the rate was correct.
>> I also tried the 3.1.3 and 3.2.0 Hypervisors and they exhibit
>> the same problem on the es7000.
>> It's not clear if is this a platform specific problem
>> or not. So far the only reports of the problem are on the
>> es7000. So for now I am running the attached patch to
>> avoid the pmtimer on es7000 only.
> Fair enough, but obviously this does need to be fixed: while not understood
> it could point to any amount of other badness or corruption happening in the
> background that we simply have not yet discovered.
>  -- Keir

I am hoping to get some feedback on a similar large
system. Limiting dom0 memory seems to be the standard
operating procedure on large memory systems so if it's
a common problem then it's being masked.


Xen-devel mailing list