WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] PATCH: Enable QEMU booting of blktap disks

To: "Gerd Hoffmann" <kraxel@xxxxxxxxxx>
Subject: Re: [Xen-devel] PATCH: Enable QEMU booting of blktap disks
From: "Andrew Warfield" <andrew.warfield@xxxxxxxxxxxx>
Date: Fri, 20 Jul 2007 06:04:19 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Delivery-date: Fri, 20 Jul 2007 06:02:33 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=gD7GfXiVn/2OUxRVWwrjSnAVeMPxzX5OLyMb1mduZ7z9b4xEYJDxdim71vVA0H343rX+qawtICyaEY0V8ApoBsv8E3dn8BfDHD32ES23rjbzkIFSx8S+bCmawMwb+mmFnd9teSJtzx1ebUD8elH9NVSrb2Um4BxAyzrJMob/4is=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=eVwX19ARmGspbsi6xk+xcxeanG9c/8afUYFwyyZLM/KOhkflSCQNPCu9eMjk+SwChVd++Ox11gnVUS5ltmil2XiuqySB8Q2r5zW5au0MqvnQrkLMbF5sRgU7esy4CxNW9U4z6uY1E5QmFOlFsLAK21Abg/ylVizhzgo8YzmJrQM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46A08FEE.70908@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20070719170922.GE26669@xxxxxxxxxx> <eacc82a40707191034j4ae8eb3ch8077977e39c92bce@xxxxxxxxxxxxxx> <46A08FEE.70908@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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