From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: PATCH: Enable QEMU booting of blktap disks
Date: Fri, 20 Jul 2007 12:35:26 +0200
Message-ID: <46A08FEE.70908@redhat.com>
References: <20070719170922.GE26669@redhat.com>
	<eacc82a40707191034j4ae8eb3ch8077977e39c92bce@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <eacc82a40707191034j4ae8eb3ch8077977e39c92bce@mail.gmail.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Andrew Warfield <andrew.warfield@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, "Daniel P. Berrange" <berrange@redhat.com>
List-Id: xen-devel@lists.xenproject.org

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