From: Wei Liu <wei.liu2@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH RFC 0/4] Allow qemu to provide emulated disks for devices with hotplug scripts
Date: Tue, 8 Mar 2016 19:18:15 +0000 [thread overview]
Message-ID: <20160308191815.GX31271@citrix.com> (raw)
In-Reply-To: <1456917244-2908-1-git-send-email-george.dunlap@citrix.com>
On Wed, Mar 02, 2016 at 11:14:00AM +0000, George Dunlap wrote:
> Qemu in dom0 can only provide emulated disks when the qemu process has
> access to an image of the file. At the moment, this only includes
> plain files or physical devices in dom0; it does not include anything
> to do with a hotplug script.
>
> However, hotplug scripts run from dom0 generally do, as a necessary
> side effect of their activity, create a block device which could be
> passed to domain 0; this block device can be passed to a qemu device
> running in dom0 to provide emulated disk support.
>
> This series allows qemu to gain access to that block device, giving it
> full parity with PV guests for all disks whose backend is in domain 0.
>
> It also takes steps towards generalizing the "local attach"
> funcitonality which is used by pygrub to access non-local disks, so
> that in the future qemu can access emulated disks by attaching them to
> dom0.
>
> RFC because I haven't tested it since forward-porting it.
>
I haven't looked at this series, but I expect another posting on top of
Ian Jackson's hotplug script interface patch.
If you want me to look at this series, please let me know.
Wei.
>
> George Dunlap (4):
> libxl: Move check for local access to a funciton
> libxl: Share logic for finding path between qemuu and pygrub
> tools/hotplug: Add a "dummy" hotplug script for testing
> libxl: Allow local access for block devices with hotplug scripts
>
> tools/hotplug/Linux/Makefile | 1 +
> tools/hotplug/Linux/block-common.sh | 5 +-
> tools/hotplug/Linux/block-dummy | 107 +++++++++++++++++++++++++++++++++
> tools/libxl/libxl.c | 115 +++++++++++++++++++++++++++++-------
> tools/libxl/libxl_bootloader.c | 1 +
> tools/libxl/libxl_dm.c | 66 ++++++++++++++-------
> tools/libxl/libxl_internal.h | 12 +++-
> 7 files changed, 262 insertions(+), 45 deletions(-)
> create mode 100644 tools/hotplug/Linux/block-dummy
>
> --
> 2.1.4
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-03-08 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 11:14 [PATCH RFC 0/4] Allow qemu to provide emulated disks for devices with hotplug scripts George Dunlap
2016-03-02 11:14 ` [PATCH RFC 1/4] libxl: Move check for local access to a funciton George Dunlap
2016-03-02 11:14 ` [PATCH RFC 2/4] libxl: Share logic for finding path between qemuu and pygrub George Dunlap
2016-03-02 11:14 ` [PATCH RFC 3/4] tools/hotplug: Add a "dummy" hotplug script for testing George Dunlap
2016-03-02 11:14 ` [PATCH RFC 4/4] libxl: Allow local access for block devices with hotplug scripts George Dunlap
2016-03-08 19:18 ` Wei Liu [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=20160308191815.GX31271@citrix.com \
--to=wei.liu2@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=xen-devel@lists.xen.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).