[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110421080638.GA10630@infradead.org>
Date: Thu, 21 Apr 2011 04:06:38 -0400
From: Christoph Hellwig <hch@...radead.org>
To: Ian Campbell <Ian.Campbell@...rix.com>
Cc: Christoph Hellwig <hch@...radead.org>,
"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
Stefano Stabellini <Stefano.Stabellini@...citrix.com>,
"jaxboe@...ionio.com" <jaxboe@...ionio.com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"konrad@...nel.org" <konrad@...nel.org>
Subject: Re: [Xen-devel] Re: [PATCH v3] xen block backend.
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. 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists