From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Xen 3.3.1 latest / starting guests causes Oops in tapdisk? Date: Thu, 28 May 2009 13:27:53 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ray Barnes , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 28/05/2009 13:14, "Ray Barnes" wrote: > Problem is present using CentOS 5.x guests using the Cent kernel also.=A0 T= he > aforementioned domU is Debian 4 though.=A0 I've tried this under 3.3.1-rele= ase > and the latest 3.3.1 from xen-3.3-testing as of two days ago with the sam= e > result.=A0 I set maxium loop devices at 255 (was 8), no change.=A0 Also, afte= r the > Oops is triggered, I can no longer start domUs (even good ones which woul= d > otherwise not exhibit the problem), until after a reboot.=A0 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