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 12:19:51 -0400
Cc:	"xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date:	Thu, 28 May 2009 09:20:28 -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=x+qlOKpVBui7xYJgk0/3+jBY0CsrbQV0uwgMnFCYNls=; b=tzvkiGG+SylxdMDHz3vKbdTrMax4geJ0HRjvej7NrJC1IQtaAgcPFzNOdPxspTvJLI xjiGJCqg1hW3DrHZD3aWXRcDkFGx4g1hIO4mJ7sQs/Xl8RK3yj9UAE5fYGBbCsLbtjoq RopY7UdHtDTBl1Q5QtRVbCtgetIJWb1NPU08c=
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=q/GEZHwDxgv148hDnksV2irI+iMJpIKuFKPYTaCc/VkDRmYVC0IUXqKRboPGj89uGQ kaC29TY0ZU6HwudokHpVCHGlDy1Q5A7E67hTRzdjUujQaVcKfU+wL4q/eyTDmY/zvPGO D0yFOlfBeW8y0Z6CVlxXJMkvj8dyd4+qNNf2w=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<C6446CC2.C166%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:	<afa5bb590905280655w1a60e5cai84553cecf37b0354@xxxxxxxxxxxxxx> <C6446CC2.C166%keir.fraser@xxxxxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Thanks, i'll switch to xen-unstable if I have problems with the workaround, which is (regrettably) to use file: instead of tap:aio: as the blkdev in the domU config files.

-Ray

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

It might be interesting to try xen-unstable which should now be switched
over to blktap2 by default. Quite apart from being interested as to how well
that works right now, I also imagine you can get quicker responses from the
developers of that. If it works, blktap2 would port over to 3.4 quite
easily. Probably 3.3 too.

-- Keir

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

> 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 <http://tical.net/> @gmail.com

>> <http://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