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


stress testing was: Re: [Xen-devel] blocking Xen 3.X production use: sof

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: stress testing was: Re: [Xen-devel] blocking Xen 3.X production use: soft lockup bugs
From: Steve Traugott <stevegt@xxxxxxxxxxxxx>
Date: Fri, 11 Aug 2006 18:46:58 -0700
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 11 Aug 2006 18:48:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C0FA1A65.27D%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: <20060804202121.GA13827@xxxxxxxxxxxxx> <C0FA1A65.27D%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Sat, Aug 05, 2006 at 09:50:29AM +0100, Keir Fraser wrote:
> On 4/8/06 9:21 pm, "Steve Traugott" <stevegt@xxxxxxxxxxxxx> wrote:
> > On Thu, Aug 03, 2006 at 09:03:18AM +0100, Keir Fraser wrote:
> >> Also older versions using sedf scheduler (which has now been patched to
> >> avoid this) could end up with domain0 consuming all CPU and starving
> >> other guests, leading to softlockup errors. We haven't seen any such
> >> errors on our own test machines since this was fixed. Of course, that
> >> doesn't mean there aren't problems with other test scenarios!
> > 
> > That is exactly what was happening.  I did more testing yesterday and
> > last night (-testing changeset 9732), and realized that I was only
> > seeing soft lockups on the second of two domU guests, and only when
> > running a heavy load in dom0.  According to 'xm vcpu-list' the second
> > guest was on CPU 0, as was the workload in dom0...  I added more
> > workload processes to consume both CPUs in dom0, and of course when I
> > did that, the first guest ground to a halt and started showing soft
> > lockups as well.
> It's *always* worth trying the tip of 3.0-testing if you're seeing problems
> with a strictly older version. In this case there are about 50 newer
> changesets, many of which are the result of aggressive testing by Suse for
> SLES10. Well worth having.

In between everything else I'm partway through a build of testing tip;
I really need to automate that, including all my local modules, some
stress tests, and so on -- ever since Xen 1.0 we've been using various
combinations of Xen, AFS, DRBD, and soon aoe, in an environment which
is apparently good at finding bugs and regression in all of the
above...  :-}

Because we rely on these things so much it would be in my best
interests to write a "daily build" style stress test harness -- if I
do this, I'd probably do a periodic post similar to Rick's and David's
xm-test results, maybe some web stats and so on.  Does this sound
like something that would be useful to other folks?

Stephen G. Traugott  (KG6HDQ)
Managing Partner, TerraLuna LLC
stevegt@xxxxxxxxxxxxx -- http://www.t7a.org

Xen-devel mailing list