Gerd, don't misunderstand what I'm saying: I'd be delighted to see
blktap and qemu share block device implementations. However, the
blktap patch that I am commenting on achieves exactly the opposite of
that: it *requires* two implementations of any virtual disk type that
you want to use PV drivers on in an HVM guest.
a.
On 7/20/07, Gerd Hoffmann <kraxel@xxxxxxxxxx> wrote:

Andrew Warfield wrote:
> As I've said before, I dislike the idea of having separate
> implementations of disks -- one in qemu and one in tapdisk.
The qemu one isn't going to go away due to qemu being *the* device model
for any kind of virtualization in Linux. So if you want to have tapdisk
share the code to avoid duplication I see two possible ways to get there:
 (a) replace blktapd with qemu
 (b) put the bits into a shared library, which then can be used by
 qemu & blktapd and other tools (qemu-img, virtual machine
 management tools, ...).
cheers,
 Gerd

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel