From: Roger Pau Monne <roger.pau@citrix.com>
To: xen-devel@lists.xenproject.org
Subject: [PATCH 0/4] libxl: fix CDROM issues
Date: Thu, 7 Apr 2016 19:45:25 +0200 [thread overview]
Message-ID: <1460051129-20817-1-git-send-email-roger.pau@citrix.com> (raw)
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
next reply other threads:[~2016-04-07 17:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 17:45 Roger Pau Monne [this message]
2016-04-07 17:45 ` [PATCH 1/4] libxl: set the device model version earlier in xenstore Roger Pau Monne
2016-04-08 13:14 ` Wei Liu
2016-04-08 14:16 ` Roger Pau Monné
2016-04-08 14:24 ` Wei Liu
2016-04-07 17:45 ` [PATCH 2/4] libxl: set the backend type to Qdisk for CDROM devices on DM HVM guests Roger Pau Monne
2016-04-08 13:29 ` Wei Liu
2016-04-07 17:45 ` [PATCH 3/4] libxl: only allow guests with a device model to use cd-{eject/insert} Roger Pau Monne
2016-04-08 13:21 ` Wei Liu
2016-04-08 14:17 ` Roger Pau Monné
2016-04-08 14:25 ` Wei Liu
2016-04-08 14:34 ` Ian Jackson
2016-04-08 14:35 ` Roger Pau Monné
2016-04-08 14:47 ` Wei Liu
2016-04-08 14:51 ` Roger Pau Monné
2016-04-08 14:59 ` Andrew Cooper
2016-04-08 15:06 ` George Dunlap
2016-04-08 15:07 ` Wei Liu
2016-04-07 17:45 ` [PATCH 4/4] libxl: remove code added to use the 'phy' backend with CDROM devices Roger Pau Monne
2016-04-08 13:30 ` Wei Liu
2016-04-08 15:07 ` Ian Jackson
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=1460051129-20817-1-git-send-email-roger.pau@citrix.com \
--to=roger.pau@citrix.com \
--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 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.