From: Gleb Natapov <gleb@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Juan Quintela <quintela@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Ryan Harper <ryanh@us.ibm.com>, Amit Shah <amit.shah@redhat.com>
Subject: Re: [Qemu-devel] CD-ROM bug round-up
Date: Wed, 30 Mar 2011 18:50:11 +0200 [thread overview]
Message-ID: <20110330165011.GF7766@redhat.com> (raw)
In-Reply-To: <AANLkTim_1kNJ6=13GpUXQBTbtjJUdAxL7=JXwCNq6W9G@mail.gmail.com>
On Wed, Mar 30, 2011 at 05:40:40PM +0100, Stefan Hajnoczi wrote:
> Several of us have been investigating CD-ROM bugs. Let's update each
> other, make sure we're not duplicating effort, and see if we can help
> each other make progress.
>
> = Stefan =
>
> Guests do not notice media change when using Linux host CD-ROM
> pass-through for two reasons:
> 1. QEMU is caching the device size for removable media and never updating it.
> 2. On Linux hosts the /dev/cdrom file descriptor needs to be reopened
> to refresh the underlying device size.
>
> Patches have been posted to qemu-devel.
>
> Libvirt does not recognize eject failure due to locked tray. This
> causes libvirt to get out-of-sync and believe the medium was
> successfully changed. A libvirt fix is in progress:
> https://bugzilla.redhat.com/show_bug.cgi?id=689101
>
> = Anthony =
>
> Using 'change' or scripted commands without a delay between closing
> the BlockDriverState and opening the new CD-ROM. The guest does not
> have a chance to poll the drive and determine a medium present ->
> medium not present transition followed by a medium not present ->
> medium present transition.
>
> A fix for this does not exist yet and might be tricky since we need to
> delay or wait for the guest to poll once before opening the new
> CD-ROM.
>
This sounds familiar and should have been fixed by commit
93c8cfd9e67a62711b86f4c93747566885eb7928
> = Amit =
>
> Found that 2.6.38 and later guest kernels fail to report media change.
> The new in-kernel media change polling framework issues ATAPI
> commands which are not implemented in hw/ide/core.c.
>
> = Juan =
>
> ATA HSM violation errors after live migration while CD-ROM read
> operations. This is probably a hw/ide/* or DMA migration bug.
>
> = Markus =
>
> ?
>
> Stefan
--
Gleb.
next prev parent reply other threads:[~2011-03-30 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 16:40 [Qemu-devel] CD-ROM bug round-up Stefan Hajnoczi
2011-03-30 16:50 ` Gleb Natapov [this message]
2011-03-30 18:07 ` Stefan Hajnoczi
2011-03-31 9:53 ` [Qemu-devel] " Amit Shah
2011-03-31 14:03 ` Stefan Hajnoczi
2011-03-31 19:44 ` [Qemu-devel] [RFC PATCH 1/3] ide: Move GET_EVENT_STATUS_NOTIFICATION command handling to its own function Amit Shah
2011-03-31 19:44 ` [Qemu-devel] [RFC PATCH 2/3] atapi: implement GET_EVENT_STATUS_NOTIFICATION command Amit Shah
2011-03-31 19:44 ` [Qemu-devel] [RFC PATCH 3/3] atapi: Allow GET_EVENT_STATUS_NOTIFICATION and TEST_UNIT_READY after media change Amit Shah
2011-03-31 9:56 ` [Qemu-devel] CD-ROM bug round-up 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=20110330165011.GF7766@redhat.com \
--to=gleb@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=ryanh@us.ibm.com \
--cc=stefanha@gmail.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;
as well as URLs for NNTP newsgroup(s).