Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: call for testing: xen 4.1 packages

On Fri, 1 Apr 2011 17:07:41 +0200, Manuel Bouyer <bouyer%antioche.eu.org@localhost> wrote:
The purpose is rather to support file formats that can offer block
device functionality, without having to (re)write their support
directly in kernel. AFAICT, vnd(4) does not support sparse files,
and qcow/raw formats are sparse. The quickest way to expose those
through a vnd(4) like interface is probably qemu-dm + pud(4).

but why do they need to be exposed as a vnd-like interface, if the
tool which will read them is already a userland process ? this
tool could read the filesystem image by itself, isn't it ?

Correct. But we are missing the glue that will translate the block requests from domU: xbd => xbdback => XXX => qemu-dm, eg. the "blocktap" interface that offers block level I/O in userland.

Jean-Yves Migeon

Home | Main Index | Thread Index | Old Index