xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Thanos Makatos <thanos.makatos@citrix.com>
To: xen-devel@lists.xensource.com
Cc: andrei.lifchits@citrix.com
Subject: [PATCH 0 of 3] blktap3/libxl: add support for blktap3 in libxl
Date: Fri, 8 Feb 2013 17:24:11 +0000	[thread overview]
Message-ID: <patchbomb.1360344251@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. Since there is no block device in dom0 any more, pygrub won't be able to
   boot from VHD files. To get around this problem, pygrub can use the NBD
   functionality (existing in blktap2.5): it can explicitly ask tapback to
   create a NDB in order to access the virtual disk. This functionality will be
   implemented in a future patch series. However, this will only work for Linux
   dom0's. As a generic solution that would work on any dom0, we could
   implement a simple protocol for data exchange between pygrub and tapdisk.

Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>

             reply	other threads:[~2013-02-08 17:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08 17:24 Thanos Makatos [this message]
2013-02-08 17:24 ` [PATCH 1 of 3] blktap3/libxl: add new device kind and disk back-end Thanos Makatos
2013-02-08 17:24 ` [PATCH 2 of 3] blktap3/libxl: Check whether blktap3 is available Thanos Makatos
2013-02-12 17:57   ` Ian Jackson
2013-02-13 10:44     ` Thanos Makatos
2013-03-05 12:58     ` Thanos Makatos
2013-03-05 13:51       ` Ian Jackson
2013-03-05 14:25         ` Thanos Makatos
2013-03-05 14:28           ` Ian Jackson
2013-03-05 14:42             ` Thanos Makatos
2013-03-05 14:53               ` Ian Jackson
2013-03-05 15:13                 ` Thanos Makatos
2013-03-05 15:27                   ` Ian Jackson
2013-03-05 15:44                     ` Thanos Makatos
2013-02-08 17:24 ` [PATCH 3 of 3] blktap3/libxl: Handles blktap3 device in libxl Thanos Makatos
2013-02-12 18:01   ` Ian Jackson
2013-02-13 11:16     ` Thanos Makatos
  -- strict thread matches above, loose matches on Subject: below --
2013-04-19 15:40 [PATCH 0 of 3] blktap3/libxl: add support for blktap3 " Thanos Makatos
2013-04-20  0:20 ` Pasi Kärkkäinen
2013-04-22  8:33   ` Thanos Makatos
2013-04-27  7:34 ` Sylvain Munaut
2013-04-29  9:58   ` Thanos Makatos
2013-05-14  8:37   ` 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.1360344251@makatos-desktop \
    --to=thanos.makatos@citrix.com \
    --cc=andrei.lifchits@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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).