public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Ryan Harper <ryanh@us.ibm.com>, Tejun Heo <tj@kernel.org>,
	Mikulas Patocka <mpatocka@redhat.com>,
	dm-devel@redhat.com, Vivek Goyal <vgoyal@redhat.com>,
	john.cooper@redhat.com, rusty@rustcorp.com.au, hch@infradead.org,
	kvm@vger.kernel.org
Subject: Re: [REGRESSION][BISECTED] virtio-blk serial attribute causes guest to hang [Was: Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm]
Date: Thu, 9 Sep 2010 13:35:54 -0500	[thread overview]
Message-ID: <20100909183554.GK30086@us.ibm.com> (raw)
In-Reply-To: <20100909175537.GA9589@redhat.com>

* Mike Snitzer <snitzer@redhat.com> [2010-09-09 12:56]:
> On Thu, Sep 09 2010 at 12:03pm -0400,
> Ryan Harper <ryanh@us.ibm.com> wrote:
> 
> > * Mike Snitzer <snitzer@redhat.com> [2010-09-09 10:58]:
> 
> > > I'm using virtio-blk w/ cache=none for the root device.  virtio-blk
> > > isn't used for any other devices in the guest.
> > 
> > And you don't have any other disks in the guest (I see just the root and
> > the cdrom), the lv stuff is happening against some sort of dummy target?
> 
> Correct.  I have used variants of the script I provided against both
> scsi-debug devices and iscsi devices in the guest.  The script I shared
> uses multipath on scsi-debug (ram-based) devices.
> 
> That script causes udev to run its various callouts via multipath and
> LVM (both packages, upstream and RHEL6, now use udev).
> 
> I have verified that I no longer get the hang if I switch the root
> device from virtio to ide.

And in the failing case, do you see:

/sys/block/vda/serial 

attribute in sysfs?


-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com

  reply	other threads:[~2010-09-09 18:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100902032246.GA31484@redhat.com>
2010-09-09 15:26 ` [REGRESSION][BISECTED] virtio-blk serial attribute causes guest to hang [Was: Re: [PATCH UPDATED 4/5] dm: implement REQ_FLUSH/FUA support for request-based dm] Mike Snitzer
2010-09-09 15:44   ` Ryan Harper
2010-09-09 15:57     ` Mike Snitzer
2010-09-09 16:03       ` Ryan Harper
2010-09-09 17:55         ` Mike Snitzer
2010-09-09 18:35           ` Ryan Harper [this message]
2010-09-09 19:15             ` Mike Snitzer
2010-09-09 19:43               ` Mike Snitzer
2010-09-09 20:14                 ` Mike Snitzer
2010-09-09 20:30                   ` Ryan Harper
2010-09-09 21:00                     ` [PATCH] virtio-blk: put request that was created to retrieve the device id Mike Snitzer
2010-09-09 21:15                       ` Christoph Hellwig
2010-09-17 14:58                         ` Ryan Harper
2010-09-21 21:00                           ` Christoph Hellwig
2010-10-08 16:06                             ` [2.6.36 REGRESSION] " Mike Snitzer
2010-10-09  1:41                       ` [PATCH] " Rusty Russell

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=20100909183554.GK30086@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=dm-devel@redhat.com \
    --cc=hch@infradead.org \
    --cc=john.cooper@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=snitzer@redhat.com \
    --cc=tj@kernel.org \
    --cc=vgoyal@redhat.com \
    /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