From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ryan Harper Subject: Re: BUG() with SCSI-interfaced disk images Date: Thu, 8 Jan 2009 08:01:03 -0600 Message-ID: <20090108140102.GF13481@us.ibm.com> References: <20081226210028.GA25127@boost.horde.net> <20090107201918.GA12071@boost.horde.net> <20090107223450.GE13481@us.ibm.com> <20090108021351.GA12570@boost.horde.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Ryan Harper , kvm@vger.kernel.org To: John Morrissey Return-path: Received: from e4.ny.us.ibm.com ([32.97.182.144]:60133 "EHLO e4.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750905AbZAHOBG (ORCPT ); Thu, 8 Jan 2009 09:01:06 -0500 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e4.ny.us.ibm.com (8.13.1/8.13.1) with ESMTP id n08Dxnm5020270 for ; Thu, 8 Jan 2009 08:59:49 -0500 Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v9.1) with ESMTP id n08E15kk119658 for ; Thu, 8 Jan 2009 09:01:05 -0500 Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n08F1GR2007120 for ; Thu, 8 Jan 2009 10:01:16 -0500 Content-Disposition: inline In-Reply-To: <20090108021351.GA12570@boost.horde.net> Sender: kvm-owner@vger.kernel.org List-ID: * John Morrissey [2009-01-07 20:16]: > On Wed, Jan 07, 2009 at 04:34:50PM -0600, Ryan Harper wrote: > > * John Morrissey [2009-01-07 15:59]: > > > On Fri, Dec 26, 2008 at 04:00:28PM -0500, John Morrissey wrote: > > > > I'm encountering a kernel BUG() in guests using SCSI-interfaced disk > > > > images. I've tried with the Debian packaging of KVM 79 and 82; both > > > > exhibit the same behavior (disclaimer: Debian has about a dozen > > > > patches in their kvm packaging, but they all seem to be changes to the > > > > build/install process or security-related). > > > > > > Not to be pushy, but does anyone have any ideas on this, or can I > > > provide any additional information? I'm afraid I'm a bit over my head > > > when debugging kernel internals. > > > > Sorry, I meant to respond. This is more than likely a SCSI emulation > > error rather than a kernel error. I've seen the error a couple of > > times, but I don't have a fix for the issue yet as I don't have a > > reliable way to reproduce the error. If you have an easy way to > > reproduce the bug, I'll see if I can figure out a fix. > > I can reproduce this reliably when fscking a filesystem in a .vmdk I have. > I can't give you the vmdk or a dump of the filesystem, but I can devote some > time to troubleshoot this if you can guide me a little. If having the vmdk > is really important, I might be able to sanitize it enough to send it to you > (hopefully not making this bug unreproducible in the process). I don't need the vmdk, but if there is some other repeatable process that can trigger this for you, getting that will allow me to recreate the issue myself. For example, installing Debian into a vmdk, reboot, and then fsck'ing from inside the vm would trigger it. Finding some sort of repeatable process that can trip the bug but without using any of your specific data would be the best way to move forward with the bug. -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx ryanh@us.ibm.com