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

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

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

from [Stefano Stabellini] [Permanent Link][Original]
To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [RFC, PATCH] docs: Block numbering and naming specification
From: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Date: Wed, 22 Sep 2010 14:01:40 +0100
Cc: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Wed, 22 Sep 2010 06:01:59 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19609.61356.872994.118171@xxxxxxxxxxxxxxxxxxxxxxxx>
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> <19609.61356.872994.118171@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Alpine 2.00 (DEB 1167 2008-08-23) 
On Wed, 22 Sep 2010, Ian Jackson wrote:
> Stefano Stabellini writes ("Re: [RFC, PATCH] docs: Block numbering and naming 
> specification"):
> > moderm PV-on-HVM drivers will map the hd* devices to /dev/xvd* etc., so
> > "hda1" in the config file results in /dev/xvda1 in the guest.
> 
> So what happens if you specify both hda and xvda in the domain config
> file ?  The document as currently written seems to contemplate this as
> a reasonable configuration.
 
the kernel won't boot but blkfront will print a warning about the problem

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  [Xen-devel] Re: [PATCH 2/4] libxl: implementing legacy xm cpuid parser, Andre Przywara
Next by Date:  Re: [Xen-devel] Problem: Pattern with vertical colored lines on the dom0 screen, Dietmar Hahn
Previous by Thread:  [Xen-devel] Re: [RFC, PATCH] docs: Block numbering and naming specification, Ian Jackson
Next by Thread:  [Xen-devel] Re: [RFC, PATCH] docs: Block numbering and naming specification, Ian Jackson
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy