All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	dron@redhat.com
Subject: Re: [Qemu-devel] [PATCH] blockdev: reset werror/rerror on drive_del
Date: Tue, 04 Jun 2013 13:32:48 -0600	[thread overview]
Message-ID: <51AE40E0.2010401@redhat.com> (raw)
In-Reply-To: <87fvwxllwo.fsf@blackfin.pond.sub.org>

[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]

On 06/04/2013 01:24 PM, Markus Armbruster wrote:
> Paolo Bonzini <pbonzini@redhat.com> writes:
> 
>> Il 04/06/2013 18:37, Markus Armbruster ha scritto:
>>> I figure the bit that can't be resolved now is letting the user switch
>>> off "stop on error" safely before a drive_del.  Even if we had a command
>>> for that, there'd still be a window between that command's execution and
>>> drive_del's.  Your patch solves the problem by having drive_del switch
>>> it off unconditionally.  Oookay, but please document it, because it's
>>> not exactly obvious.
>>
>> It is not obvious, but it is not surprising either when you see it (i.e.
>> you won't really be surprised by the errors in the guest and won't need
>> to know that, under the hood, rerror has been changed from the value you
>> specified).
>>

> This is drive_add's documentation in hmp-commands.hx:
> 
>     Remove host block device.  The result is that guest generated IO is
>     no longer submitted against the host device underlying the disk.
>     Once a drive has been deleted, the QEMU Block layer returns -EIO
>     which results in IO errors in the guest for applications that are
>     reading/writing to the device.
> 
> Suggest to add:
> 
>     These errors are always reported to the guest, regardless of the
>     drive's error actions (drive options rerror, werror).
> 
> Independently, libvirt needs fixing.

Total agreement that libvirt needs to use a saner disk hot-unplug
sequence when it is known that qemu provides one.  I've filed
https://bugzilla.redhat.com/show_bug.cgi?id=970761
to remind us to fix libvirt.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

  reply	other threads:[~2013-06-04 19:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03 14:58 [Qemu-devel] [PATCH] blockdev: reset werror/rerror on drive_del Stefan Hajnoczi
2013-06-03 15:20 ` Paolo Bonzini
2013-06-04 16:37 ` Markus Armbruster
2013-06-04 17:04   ` Paolo Bonzini
2013-06-04 19:24     ` Markus Armbruster
2013-06-04 19:32       ` Eric Blake [this message]
2013-06-05  7:09         ` Markus Armbruster
2013-06-05  8:21   ` Stefan Hajnoczi
2013-06-05  8:26 ` Fam Zheng

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=51AE40E0.2010401@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=dron@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.