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] Allow blktap to be able to be booted assystem vo

To: Kasai Takanori <kasai.takanori@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Allow blktap to be able to be booted assystem volume for PV-on-HVM
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Mon, 9 Jul 2007 14:47:59 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 09 Jul 2007 06:46:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <02c701c7c1e7$cc6b2ad0$dab2220a@VF03007L>
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: <4e4701c7bfbb$c7a8b360$dab2220a@VF03007L> <20070706132758.GD4286@xxxxxxxxxx> <02c701c7c1e7$cc6b2ad0$dab2220a@VF03007L>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Mon, Jul 09, 2007 at 02:09:47PM +0900, Kasai Takanori wrote:
> >It also doesn't take account of
> >fact that the device may be named 'xvda' rather than 'hda'.
> 
> I saw the presented patches. The xvdN was forcedly looked like the hdN.
> For example, the hdc is a special device named CDROM in qemu-dm.

No that is wrong. Any hdX device can be a CDROM - whether it is a CDROM
or not is determined by the :cdrom postfix, not the device name.

eg You can happily make hdc a harddisk:

   tap:aio:/var/lib/xen/images/dom.img,hdc,w

Or make hda a CDROM

   tap:aio:/var/lib/xen/images/dom.img,hda:cdrom,w


> Therefore, I think that it should not forcedly do it because it cannot take 
> the consistency.

Being able to use 'xvd*', as well as 'hd*' or 'sd*' as device names is 
important for consistency with paravirt guests, where xvd* is the 
recommended default.

> I think the HVM domain to be should boot on the hda as it is a 
> specification of qemu-dm.

It can do that. My patch made it possible to use either

   tap:aio:/var/lib/xen/images/dom.img,hda,w

Or

   tap:aio:/var/lib/xen/images/dom.img,xvda,w

At the user's choice. 

n/
-- 
|=- 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