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: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Subject: Re: [Xen-devel] PATCH: Enable QEMU booting of blktap disks
From: "Andrew Warfield" <andrew.warfield@xxxxxxxxxxxx>
Date: Thu, 19 Jul 2007 10:34:12 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 19 Jul 2007 10:31:58 -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=WWIbCxs/m0DODebiZtirVkHIh5PkqEZkA97mk9SUSdDW0AoA7lDa3SdQ32HbrhzwjBJ/VXjkzFGdFj8lFrvr0Qvvip0aI6rfdXE8HPEH9M6mjA/WLVmFvTxTY3vKVJqjz+T2r0DT8xlL6/ZWb06LBZqNfNbJLrVOkk9mi3WaJIM=
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=RlvooSAYw6+esUoLTWh44MKAOP32fH4/vqGYodwNQh1Hw4ZGnkUZqXike0hIndvBtmHRoz/K9YNPhbsCsS6gq+d3mNTsmKYBXNPl4jnNCNGFUULV3fpdcsBcef9OVrRFMFkh3xNfDuDL7nGqXuX0aYOlJOG/zQDMF7nAgvP0kDo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070719170922.GE26669@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
So two comments on this:

In the other thread that's currently going on this topic, it sounds
like others are quite successfully using the phantom code.  Why is it
broken for you?

As I've said before, I dislike the idea of having separate
implementations of disks -- one in qemu and one in tapdisk.  We'd
quite like to encourage people to be able to extend virtual block
devices in the future, and it seems like your approach is going to
force them to do two independent implementations of things.  It also
leads to complications if you want to add things like caching, shared
ramdisks, etc.  If phantom is broken, why don't we just fix that?

a.

On 7/19/07, Daniel P. Berrange <berrange@xxxxxxxxxx> wrote:
This is a re-send of previous patches:

http://lists.xensource.com/archives/html/xen-devel/2007-06/msg01021.html

The only change is that it explicitly looks for the driver type in xenstore
rather than assuming 'xvd' == 'tap' - this is because tap could be configured
with 'hd' or 'sd' nodenames too, and we still need to strip the leading
':aio' or ':vmdk', etc prefix from the path.

There are two patches:

  - xen-revert-phantom-2.patch  removes the phantom device code since it
    doesn't work & is redundant if QEMU can process tap devices straight
    from xenstore

  - xen-qemu-blktap-2.patch makes QEMU able to handle disks with xvd prefix
    treating them as IDE. Also makes QEMU strip the driver type prefix from
    tap disks since it can auto-guess driver


   Signed-off-by: Daniel P. Berrange <berrange@xxxxxxxxxx>

Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=|

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




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