xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Thanos Makatos <thanos.makatos@citrix.com>
Cc: Darren Shepherd <darren.s.shepherd@gmail.com>,
	"Fajar A. Nugraha" <list@fajar.net>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: blktap3 as a block device?
Date: Mon, 26 Nov 2012 12:48:11 +0100	[thread overview]
Message-ID: <50B356FB.70601@citrix.com> (raw)
In-Reply-To: <4B45B535F7F6BE4CB1C044ED5115CDDE012D552FE2E3@LONPMAILBOX01.citrite.net>

On 26/11/12 11:54, Thanos Makatos wrote:
> 
> 
>> -----Original Message-----
>> From: Ian Campbell
>> Sent: 26 November 2012 10:45
>> To: Darren Shepherd
>> Cc: Fajar A. Nugraha; xen-devel@lists.xen.org; Thanos Makatos
>> Subject: Re: [Xen-devel] blktap3 as a block device?
>>
>> On Sat, 2012-11-24 at 01:08 +0000, Darren Shepherd wrote:
>>> The more direct question is going forward with blktap3 is there going
>>> to be a way to see the blktap device as a block device in dom0?
>>
>> There will have to be, e.g. to support pygrub and similar uses.
>>
>> I'm not sure what form this will eventually take though (CCing Thanos,
>> blktap3 maintainer). Ideas which I've heard floating about are to have
>> tapdisk export an nbd server or supporting running a vbd device in dom0
>> in a loopback type mode.
> 
> Yes this is one of the possibilities; this functionality is already on blktap2.5 (where blktap3 is based on).
> 
> Another idea could be to use both blkfront and tapdisk on dom0, haven't considered that thoroughly though.

>From my point of view using blkfront on Dom0 should be used instead of
nbd. nbd is Linux specific, on the other hand all Dom0s have a blkfront
implementation.

  reply	other threads:[~2012-11-26 11:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-24  0:31 blktap3 as a block device? Darren Shepherd
2012-11-24  0:39 ` Fajar A. Nugraha
2012-11-24  1:08   ` Darren Shepherd
2012-11-26 10:45     ` Ian Campbell
2012-11-26 10:54       ` Thanos Makatos
2012-11-26 11:48         ` Roger Pau Monné [this message]
2012-11-26 19:50     ` Stefano Stabellini

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=50B356FB.70601@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=darren.s.shepherd@gmail.com \
    --cc=list@fajar.net \
    --cc=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).