From: Blue Swirl <blauwirbel@gmail.com>
To: Juergen Lock <nox@jelal.kn-bremen.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH:] FreeBSD host physical cdrom fixes
Date: Sat, 28 Mar 2009 22:18:04 +0200 [thread overview]
Message-ID: <f43fc5580903281318k1be21a0h5f6d91a1629c72@mail.gmail.com> (raw)
In-Reply-To: <200903282007.n2SK7QqK093818@saturn.kn-bremen.de>
On 3/28/09, Juergen Lock <nox@jelal.kn-bremen.de> wrote:
> In article <f43fc5580903280140ie068b79sd0aef2c11bfcaff8@mail.gmail.com> you write:
> >On 3/24/09, Juergen Lock <nox@jelal.kn-bremen.de> wrote:
> >> This improves physical cdrom support on FreeBSD hosts to be almost as
> >> good as on Linux, with the only notable exception that you still need to
> >> either have the guest itself eject the disc if you want to take it
> >> out/change it, or do a change command in the monitor after taking out
> >> a disc in case a guest cannot eject it itself - otherwise the guest may
> >> continue using state (like size) of the old disc.
> >>
> >> [Yes this is not perfect but still is way better than the old state of
> >> things and thus commit-worthy in my opinion. I don't think it needs
> >> to be committed in incremental pieces, if you disagree please say so.]
> >
> >Thanks, applied.
>
>
> Thanx! Is anyone looking at my scsi disk/cdrom fixes/improvements series
> also?
> http://lists.gnu.org/archive/html/qemu-devel/2009-03/msg01110.html
> Without it for example eject won't work on emulated scsi cdroms i.e.
> you'd still have to use the monitor...
Yes I'm looking, but I'm not sure if the problems I see result from
other stuff or your patches.
next prev parent reply other threads:[~2009-03-28 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 22:46 [Qemu-devel] [PATCH:] FreeBSD host physical cdrom fixes Juergen Lock
2009-03-28 8:40 ` Blue Swirl
2009-03-28 20:07 ` Juergen Lock
2009-03-28 20:18 ` Blue Swirl [this message]
2009-03-29 12:42 ` Juergen Lock
2009-03-29 15:13 ` Blue Swirl
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=f43fc5580903281318k1be21a0h5f6d91a1629c72@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=nox@jelal.kn-bremen.de \
--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 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).