From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
"jaxboe@fusionio.com" <jaxboe@fusionio.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"konrad@kernel.org" <konrad@kernel.org>
Subject: Re: [Xen-devel] Re: [PATCH v3] xen block backend.
Date: Thu, 21 Apr 2011 09:38:31 +0100 [thread overview]
Message-ID: <1303375111.5997.341.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <20110421080638.GA10630@infradead.org>
On Thu, 2011-04-21 at 09:06 +0100, Christoph Hellwig wrote:
> On Thu, Apr 21, 2011 at 09:03:23AM +0100, Ian Campbell wrote:
> > BTW about the only nice property blktap has as it currently stands over
> > this plan is that it exports an actual block device from vhd, qcow etc
> > files (in some sense blktap is a loopback driver for complex disk image
> > file formats). It turns out to occasionally be quite useful to be able
> > to mount such files, even on non-virtualisation systems (in its current
> > incarnation blktap has no dependency on Xen).
>
> You can already do that using qemu-nbd today.
Good to know, I'd had a vague feeling this was possible but hadn't
looked into how.
> In most cases the image format support in qemu is much better than in the various Xen trees
> anyway, with vhd beeing the only one that looks potentially better in Xen.
That's about what I reckon too.
Ian.
next prev parent reply other threads:[~2011-04-21 8:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 21:05 Konrad Rzeszutek Wilk
2011-04-20 21:05 ` [PATCH] xen block backend driver Konrad Rzeszutek Wilk
2011-04-21 3:40 ` Christoph Hellwig
2011-04-21 19:03 ` [Xen-devel] " Daniel Stodden
2011-04-21 19:06 ` Christoph Hellwig
2011-04-21 19:14 ` Daniel Stodden
2011-04-22 9:09 ` Christoph Hellwig
2011-05-02 19:08 ` [Xen-devel] Re: [PATCH] xen block backend driver. - proper flush/barrier/fua support missing Konrad Rzeszutek Wilk
2011-04-21 3:37 ` [PATCH v3] xen block backend Christoph Hellwig
2011-04-21 7:28 ` [Xen-devel] " Ian Campbell
2011-04-21 8:03 ` Ian Campbell
2011-04-21 8:06 ` Christoph Hellwig
2011-04-21 8:38 ` Ian Campbell [this message]
2011-04-21 8:04 ` Christoph Hellwig
2011-04-27 22:06 ` Konrad Rzeszutek Wilk
2011-04-28 19:29 ` Pasi Kärkkäinen
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=1303375111.5997.341.camel@zakaz.uk.xensource.com \
--to=ian.campbell@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=hch@infradead.org \
--cc=jaxboe@fusionio.com \
--cc=konrad.wilk@oracle.com \
--cc=konrad@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®