From: Thanos Makatos <thanos.makatos@citrix.com>
To: xen-devel@lists.xen.org
Cc: thanos.makatos@citrix.com
Subject: [PATCH 0 of 4 v2] blktap3/libxl: add support for blktap3 in libxl
Date: Mon, 15 Jul 2013 12:45:17 +0100 [thread overview]
Message-ID: <patchbomb.1373888717@makatos-desktop> (raw)
This patch series implements support for blktap3 in libxl.
Supporting blktap3 requires rather few changes:
1. We introduce a new disk back-end type (TAP3) and a new device kind (VBD3) to
allow blktap3 to co-exist with blktap3. blktap2 remains the default back-end
for tap devices. Switching in the future to blktap3 as the default handler
of tap devices should be trivial.
2. libxl doesn't spawn the tapdisk process any more, as is the case for
blktap2, since the tapback daemon is responsible for that. Thus, libxl only
needs to write to XenStore the file/partition/whatever backing the virtual
disk so that the tapback daemon can pass it to tapdisk.
3. Booting with pygrub from VHD files is trivially done by attaching blkfront
to dom0.
Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>
---
Changed since v1:
* Check whether tapback's control socket exists instead of checking whether
a process named "tapback" exists.
* Don't duplicate code for writing the type:/path/to/file to XenStore.
Changed since v2:
* Support for booting from RAW and VHD images using pygrub.
next reply other threads:[~2013-07-15 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 11:45 Thanos Makatos [this message]
2013-07-15 11:45 ` [PATCH 1 of 4 v2] blktap3/libxl: add new device kind and disk back-end Thanos Makatos
2013-07-15 11:45 ` [PATCH 2 of 4 v2] blktap3/libxl: Check whether blktap3 is available Thanos Makatos
2013-07-15 11:45 ` [PATCH 3 of 4 v2] blktap3/libxl: Handles blktap3 device in libxl Thanos Makatos
2013-07-15 11:45 ` [PATCH 4 of 4 v2] blktap3/libxl: pygrub support for RAW and VHD images Thanos Makatos
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=patchbomb.1373888717@makatos-desktop \
--to=thanos.makatos@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).