From: Markus Armbruster <armbru@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Amit Shah <amit.shah@redhat.com>,
kwolf@redhat.com, qemu-devel <qemu-devel@nongnu.org>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] block bug: tray status is not updated (and/or guest ignores it)
Date: Fri, 27 May 2011 16:35:24 +0200 [thread overview]
Message-ID: <m3d3j42our.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <20110527134112.GK22589@redhat.com> (Daniel P. Berrange's message of "Fri, 27 May 2011 14:41:12 +0100")
"Daniel P. Berrange" <berrange@redhat.com> writes:
> On Fri, May 27, 2011 at 10:39:35AM -0300, Luiz Capitulino wrote:
>> On Fri, 27 May 2011 18:10:08 +0530
>> Amit Shah <amit.shah@redhat.com> wrote:
[...]
>> > What's weird though is 'eject' in the monitor makes the cdrom go away
>> > -- a subsequent mount in the guest results in a no medium error. I
>> > thought we had solved that, Markus?
>> >
>> > By not doing a bdrv_close() in the do_eject()->eject_device() call
>> > path this starts working as expected.
>>
>> Yes, also note that with the -f option eject is capable of purging
>> any block device. I wonder if libvirt (or any client) relies on this.
>
> libvirt will only issue 'eject' on devices which are CDROMs, or Floppy,
> never hard disks, etc.
Any use of -f? Recommend to stay away from it.
https://bugzilla.redhat.com/show_bug.cgi?id=676528
next prev parent reply other threads:[~2011-05-27 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 18:29 [Qemu-devel] block bug: tray status is not updated (and/or guest ignores it) Luiz Capitulino
2011-05-27 11:31 ` Amit Shah
2011-05-27 11:34 ` Amit Shah
2011-05-27 12:40 ` Amit Shah
2011-05-27 13:39 ` Luiz Capitulino
2011-05-27 13:41 ` Daniel P. Berrange
2011-05-27 14:35 ` Markus Armbruster [this message]
2011-05-27 18:07 ` Daniel P. Berrange
2011-05-27 14:30 ` Markus Armbruster
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=m3d3j42our.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=amit.shah@redhat.com \
--cc=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.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 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.