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/
Home Products Support Community News


[Xen-devel] Re: [RFC, PATCH] docs: Block numbering and naming specificat

To: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [RFC, PATCH] docs: Block numbering and naming specification
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Wed, 29 Sep 2010 09:59:17 +0100
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Wed, 29 Sep 2010 02:01:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1285750040.16095.37718.camel@xxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <19608.52762.208166.889787@xxxxxxxxxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.1009221223330.2721@kaball-desktop> <1285750040.16095.37718.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)
On Wed, 29 Sep 2010, Ian Campbell wrote:
> How does one boot in this case then? The current behaviour is that you
> get both xvd* and hd* when you ask for only xvd*. I agree that this is
> nasty but it is how it works today so we should at least document what
> the correct configuration is if we are going to deprecate it.
> Is the correct configuration in this case to have both? e.g.:
>       disk = ['phy:/dev/VG/VM,xvda,w', 'phy:/dev/VG/VM,hda,w']
I think we should choose a behavior and be consistent, so it would be
probably clearer if in that case you get both devices, and in this case:

        disk = ['phy:/dev/VG/VM,xvda,w', 'phy:/dev/VG/VM,xvdb,w']

your guest doesn't boot.

Xen-devel mailing list