Re: [Xen-devel] Xen 3.3.1 latest / starting guests causes Oops i

To:	Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject:	Re: [Xen-devel] Xen 3.3.1 latest / starting guests causes Oops in tapdisk?
From:	Ray Barnes <tical.net@xxxxxxxxx>
Date:	Thu, 28 May 2009 09:55:35 -0400
Cc:	"xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date:	Thu, 28 May 2009 06:56:04 -0700
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=T2fmk/78Px2cKrOBO5gwP09cAcMP9WFRooIgziUq0C8=; b=jZ+ey17jpWy8snJUYCp01gf/fwJRt+3GKURf+iilUbQP+YmLV+93P9m9t+tbBV1/KB XvCg+O+xlByk1Q/m9fqu5A+KEsdy1KQs8jya5qyVOiBZ4mYhcgvCd5mGao11QquzKU9Z wu1cDvX51dEMN6hbZBJQZDxtd3g2OqQSphspw=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Vse4r79mE9Iml4rGlmdSZe7ZJEdX1TwkU7TbcJHzvApkVblU4K9E2Dp34Aelz1nQ+O XWwOE7SPkSxNG4AIdHuctk6KkS/5BW+tqREPPxlt06ueKZOvaCPmJ3HchvoluoNFtZ/g wDEgrT8qaO9ubPbAI/MIHvaRaxmKKNWBYzQEY=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<C64441D9.C12E%keir.fraser@xxxxxxxxxxxxx>
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>
References:	<afa5bb590905280514i3783f9b8p77200ad68e793a5d@xxxxxxxxxxxxxx> <C64441D9.C12E%keir.fraser@xxxxxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Thanks Keir. I've been using the supplied 2.6.18-8 kernels from your source repository throughout this issue. I just tried 3.4.0-release and the latest 3.4.0 from a pull this morning, no change. Perhaps there's some way (other than abandoning blktap-backed guests) that I can work around it?

-Ray

On Thu, May 28, 2009 at 8:27 AM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:

On 28/05/2009 13:14, "Ray Barnes" <tical.net@gmail.com> wrote:

> Problem is present using CentOS 5.x guests using the Cent kernel also. The
> aforementioned domU is Debian 4 though. I've tried this under 3.3.1-release
> and the latest 3.3.1 from xen-3.3-testing as of two days ago with the same
> result. I set maxium loop devices at 255 (was 8), no change. Also, after the
> Oops is triggered, I can no longer start domUs (even good ones which would
> otherwise not exhibit the problem), until after a reboot. Is this a Xen
> problem, or should I be looking at the OS or something else?

Probably it's a dom0 kernel issue, in the blktap device driver.

-- Keir

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

WARNING - OLD ARCHIVES

xen-devel

Re: [Xen-devel] Xen 3.3.1 latest / starting guests causes Oops in tapdi