From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
George Dunlap <dunlapg@umich.edu>,
Ian.Jackson@eu.citrix.com
Subject: Re: [PATCH v2 0/4] libxl: fix CDROM issues
Date: Fri, 8 Apr 2016 18:55:42 +0200 [thread overview]
Message-ID: <alpine.OSX.2.20.1604081852130.18723@mac> (raw)
In-Reply-To: <alpine.OSX.2.20.1604081837070.18723@mac>
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
On Fri, 8 Apr 2016, Roger Pau Monné wrote:
> On Fri, 8 Apr 2016, George Dunlap wrote:
> > BTW, I tested v1 of this series and everything seems sorted out. On
> > the basis that the only changes are superficial:
> >
> > Tested-by: George Dunlap <george.dunlap@citrix.com>
>
> Thanks, FWIW I've also pushed the series to a git branch:
>
> git://xenbits.xen.org/people/royger/xen.git fix_cdrom_v2
Sorry, I've pushed a new one with George's Tested-by tag added:
git://xenbits.xen.org/people/royger/xen.git fix_cdrom_v2.1
> >
> > On Fri, Apr 8, 2016 at 5:13 PM, Roger Pau Monne <roger.pau@citrix.com> wrote:
> > > Due to recent changes (and intended fixes) CDROM has become quite unstable
> > > recently. This series aims to fix the issues reported with having empty
> > > CDROM devices in the HVM guest configuration files. It also contains some
> > > cleanups of more generic code in order to ease the implementation.
> > >
> > > After some talk on IRC, the easiest solution at this point in the release is
> > > to force PV CDROM backends of HVM guests with a device model to use Qdisk,
> > > since the cd-{insert/eject} implementation is only able to deal with this
> > > kind of PV backend.
> > >
> > > Roger.
> > >
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xen.org
> > > http://lists.xen.org/xen-devel
> >
>
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-04-08 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 16:13 [PATCH v2 0/4] libxl: fix CDROM issues Roger Pau Monne
2016-04-08 16:13 ` [PATCH v2 1/4] libxl: set the device model version earlier in xenstore Roger Pau Monne
2016-04-08 16:13 ` [PATCH v2 2/4] libxl: set the backend type to Qdisk for CDROM devices on DM HVM guests Roger Pau Monne
2016-04-08 16:13 ` [PATCH v2 3/4] libxl: only allow guests with a device model to use cd-{eject/insert} Roger Pau Monne
2016-04-08 16:13 ` [PATCH v2 4/4] libxl: remove code added to use the 'phy' backend with CDROM devices Roger Pau Monne
2016-04-08 16:24 ` Wei Liu
2016-04-08 16:23 ` [PATCH v2 0/4] libxl: fix CDROM issues George Dunlap
2016-04-08 16:37 ` Roger Pau Monné
2016-04-08 16:55 ` Roger Pau Monné [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=alpine.OSX.2.20.1604081852130.18723@mac \
--to=roger.pau@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=dunlapg@umich.edu \
--cc=xen-devel@lists.xenproject.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).