public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: John Morrissey <jwm@horde.net>
Cc: Ryan Harper <ryanh@us.ibm.com>, kvm@vger.kernel.org
Subject: Re: BUG() with SCSI-interfaced disk images
Date: Thu, 8 Jan 2009 08:01:03 -0600	[thread overview]
Message-ID: <20090108140102.GF13481@us.ibm.com> (raw)
In-Reply-To: <20090108021351.GA12570@boost.horde.net>

* John Morrissey <jwm@horde.net> [2009-01-07 20:16]:
> On Wed, Jan 07, 2009 at 04:34:50PM -0600, Ryan Harper wrote:
> > * John Morrissey <jwm@horde.net> [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

  reply	other threads:[~2009-01-08 14:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-26 21:00 BUG() with SCSI-interfaced disk images John Morrissey
2009-01-07 20:19 ` John Morrissey
2009-01-07 22:34   ` Ryan Harper
2009-01-08  2:13     ` John Morrissey
2009-01-08 14:01       ` Ryan Harper [this message]
2009-01-08 18:15         ` John Morrissey
2009-01-08 19:24 ` qcow2 corruption? John Morrissey
2009-01-08 20:10   ` Ryan Harper
2009-01-08 20:16     ` John Morrissey
2009-01-08 20:33   ` Anthony Liguori
2009-01-09  3:42     ` John Morrissey
2009-01-09 13:34       ` Ryan Harper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090108140102.GF13481@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=jwm@horde.net \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox