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

[Ray Barnes <tical.net@xxxxxxxxx>]

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