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] Re: [Xen-users] Xen 4.1.1 crash when manipulating cpupoo

To: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-users] Xen 4.1.1 crash when manipulating cpupools.
From: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
Date: Thu, 21 Jul 2011 15:15:34 +0200
Cc: George Dunlap <george.dunlap@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx, andrewpitman@xxxxxxxxxxx
Delivery-date: Thu, 21 Jul 2011 06:16:06 -0700
Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=juergen.gross@xxxxxxxxxxxxxx; q=dns/txt; s=s1536b; t=1311254136; x=1342790136; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=NT4owq39LSl+yAT/tpfoqvFhktnyICYwxs2G5ENavJI=; b=kdPepu//2sCsGn0AEKzn40W+3VZW8wPQXvYftXs8vomB0vYFINkCSv2s armRoXa9KunkKG69PRRP4Td4NQmP0ByILFSW/ycpaBYPmLfpx03PjZlGJ yN4fS4y/FkTOOYaC4Yp7uD4hGL9rJeyCNmqW/m+BwzSmkGouTl/yxs3xL OuCnMt+XGS2OgvHzBmWMz5n+G0DGC9xJPKM8oVZ7rGhEP8+FUdQkHn8Tg XSVq2C0EsuMNSyhnTXNa+NjG700iW;
Domainkey-signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Message-ID:Date:From:Organization: User-Agent:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=n6J1kL18QXs2IWljM2l4YsRKM11KdyvjeBE5blrrldk/aTs8PZlGwIRM iZEMm0Kax/nAQpXajrzPBkEywUjfTaR/gN1dy306YKehM7MCI888UyIw2 CuVpywAO1oH+/UhTfaVlJhPsXNOSbrD9idO8c64+ftSzV4iK7/ahhfyYf ZXS43289nemep3Tkeg3Co1Z6VjmAl8xptXYGIZaMI4L9stU2bXp1Q8skD tb82y/HOswtG/bGNp0BCAK2BfQZy0;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110721125857.GV32373@xxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Fujitsu Technology Solutions
References: <95606920.636453.1310736697756.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1324163226.639762.1310740209589.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20110721125857.GV32373@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110626 Iceowl/1.0b2 Icedove/3.1.11
On 07/21/11 14:58, Pasi Kärkkäinen wrote:
On Fri, Jul 15, 2011 at 02:30:09PM +0000, andrewpitman@xxxxxxxxxxx wrote:
    Hi all!

    I've been trying to make use of the credit2 scheduler for my guests
    running real-time (audio) applications, and to facilitate this I'm using
    cpupools to separate Domain-0 and less time critical guests which run fine
    under the regular credit scheduler, and the others which need to use
    credit2.  However, I seem to be able to reliably crash the hypervisor when
    I try to move virtual cpus (hyperthreads) or domains between cpupools.
    Sometimes it even crashes when I simply try to set the credit2 scheduler
    weight for a domain.  All domains are fully virtualized and running CentOS
    5.  Dom-0 is running Fedora 13 with pvops kernel.

    The panic message displays a register dump and stack trace, as well as:
    (XEN) Panic on CPU 0:
    (XEN) Xen BUG at sched_credit.c:991

    Hardware is a Dell R810 server with one 10-core Xeon E7, 128 GB RAM and
    the guests reside on NAS storage.

    If I simply use Pool-0 for everything and set the default scheduler to
    credit2 in the Xen boot string everything runs fine, but this workaround
    is not ideal since it removes some flexibility for me.

    Any ideas where I should look to determine how to resolve this?

You could try to make credit2 cpupool-ready ;-)

I don't think credit2 is supporting cpupools up to now (at least not any other
cpupool than Pool-0). George?

I wanted to address this topic on the upcoming Xen Hackathon here in Munich, as
George will be here, too, to answer my questions...

Hope you can wait until then...
As I'm very busy now, I won't have much time to look into this earlier.


Juergen Gross                 Principal Developer Operating Systems
PDG ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@xxxxxxxxxxxxxx
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>