qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	Juan Quintela <quintela@redhat.com>,
	qemu-devel@nongnu.org, Ryan Harper <ryanh@us.ibm.com>,
	Amit Shah <amit.shah@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/3] block: Correct size across CD-ROM media change
Date: Wed, 30 Mar 2011 11:06:50 +0100	[thread overview]
Message-ID: <AANLkTimnwcPKT2TpZg5XWhVbupTd6vbdaEd8AsJrA_o7@mail.gmail.com> (raw)
In-Reply-To: <m3pqp9ror6.fsf@blackfin.pond.sub.org>

On Wed, Mar 30, 2011 at 9:33 AM, Markus Armbruster <armbru@redhat.com> wrote:
> Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> writes:
>
>> This patch series fixes two Linux host CD-ROM pass-through bugs in QEMU.
>>
>> After applying these patches it is possible to pass-through a Linux host CD-ROM
>> completely.  The guest can eject from software or the physical eject button can
>> be pressed on the drive.  The guest can detect this and newly inserted media
>> are noticed.  There is no need to issue any QEMU monitor 'eject' or 'change'
>> commands because the host CD-ROM is completely "passed through".
>
> Things can get confusing here, as "eject" is an overloaded term :)
>
> Let me try to preempt such confusion.  We have three separate actions to
> consider: OS opening and closing the tray, and QEMU monitor commands
> "eject" and "change", and the user inserting/removing media from a
> physical tray.
>
> On bare metal, OS open/close tray affects the physical tray the obvious
> way.  The user can insert/remove media while the tray is open.
>
> A virtual CD-ROM is backed by a QEMU block device (the things "info
> block" shows).  The block device can be empty (seen by the gues OS as
> "no media"), or it can be connected to a file.  Monitor commands "eject"
> and "change" manipulate that connection.
>
> Guest OS open/close tray affects the virtual tray the obvious way.  In
> particular, if the OS opens, then closes the tray, it gets the same
> media back, unless the user changed it[*].
>
> Normally, a block device's file is an image file.  Monitor commands
> "eject" and "change" are seen by the guest OS as media change.
>
> Besides image files, we can also use host block devices.  This adds
> another way to change media: The user can insert/remove physical media
> while the physical tray is open.
>
> Regardless, monitor commands "eject" and "change" still work, and are
> still seen by the guest OS as media change.

I agree with your description.

These patches improve Linux host CD-ROM pass-through.  They do not
help ISO CD-ROM weirdness but I'm interested in seeing what CD-ROM
issues you're investigating.

Stefan

      reply	other threads:[~2011-03-30 10:06 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 19:04 [Qemu-devel] [PATCH v2 0/3] block: Correct size across CD-ROM media change Stefan Hajnoczi
2011-03-29 19:04 ` [Qemu-devel] [PATCH v2 1/3] trace: Trace bdrv_set_locked() Stefan Hajnoczi
2011-03-29 19:04 ` [Qemu-devel] [PATCH v2 2/3] block: Do not cache device size for removable media Stefan Hajnoczi
2011-03-29 19:04 ` [Qemu-devel] [PATCH v2 3/3] raw-posix: Re-open host CD-ROM after media change Stefan Hajnoczi
2011-03-31 10:05   ` [Qemu-devel] " Kevin Wolf
2011-04-01 14:09     ` Stefan Hajnoczi
2011-04-03 11:57   ` [Qemu-devel] " Stefan Hajnoczi
2011-04-03 13:12     ` Blue Swirl
2011-04-03 18:06       ` Stefan Hajnoczi
2011-04-04 10:47         ` [libvirt] " Daniel P. Berrange
2011-04-04 12:58           ` Stefan Hajnoczi
2011-04-04 13:02           ` Anthony Liguori
2011-04-04 13:16             ` Daniel P. Berrange
2011-04-04 14:19               ` Anthony Liguori
2011-04-04 14:26                 ` Daniel P. Berrange
2011-04-04 14:43                   ` Anthony Liguori
2011-04-04 16:38                     ` Blue Swirl
2011-04-04 13:22     ` Avi Kivity
2011-04-04 13:38       ` Anthony Liguori
2011-04-04 13:49         ` Avi Kivity
2011-04-04 15:09           ` Stefan Hajnoczi
2011-04-04 15:11             ` Avi Kivity
2011-04-05  6:41             ` Amit Shah
2011-04-05  7:48               ` Avi Kivity
2011-04-05  8:09                 ` Amit Shah
2011-04-05  9:00                   ` Avi Kivity
2011-04-05  9:12                     ` Amit Shah
2011-04-05  9:17                       ` Avi Kivity
2011-04-05  9:26                         ` Amit Shah
2011-04-06  8:07                         ` Amit Shah
2011-04-05  8:40               ` Stefan Hajnoczi
2011-04-05  8:58                 ` Amit Shah
2011-04-04 17:54         ` David Ahern
2011-04-05  5:33           ` Stefan Hajnoczi
2011-04-05  5:42             ` David Ahern
2011-04-05 12:41               ` Stefan Hajnoczi
2011-03-30  8:33 ` [Qemu-devel] [PATCH v2 0/3] block: Correct size across CD-ROM " Markus Armbruster
2011-03-30 10:06   ` Stefan Hajnoczi [this message]

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=AANLkTimnwcPKT2TpZg5XWhVbupTd6vbdaEd8AsJrA_o7@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=amit.shah@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=ryanh@us.ibm.com \
    --cc=stefanha@linux.vnet.ibm.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).