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


Re: [Xen-devel] Re: Question on "xen-blkfront: handle Xen major numbers

To: Stefan Bader <stefan.bader@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: Question on "xen-blkfront: handle Xen major numbers other than XENVBD"
From: John Haxby <john.haxby@xxxxxxxxxx>
Date: Wed, 13 Jul 2011 18:25:21 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Wed, 13 Jul 2011 10:26:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E1DC57D.3010002@xxxxxxxxxxxxx>
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: <4E1D6A48.1020801@xxxxxxxxxxxxx> <alpine.DEB.2.00.1107131143440.12963@kaball-desktop> <1310554481.634.381.camel@xxxxxxxxxxxxxxxxxxxxxx> <4E1D8C1C.1040200@xxxxxxxxxxxxx> <alpine.DEB.2.00.1107131409210.12963@kaball-desktop> <4E1DA16E.6020302@xxxxxxxxxxxxx> <alpine.DEB.2.00.1107131626510.12963@kaball-desktop> <4E1DC57D.3010002@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110428 Fedora/3.1.10-1.fc15 Lightning/1.0b3pre Thunderbird/3.1.10
On 13/07/11 17:19, Stefan Bader wrote:
> So for HVM they would be called hda in the cfg but sda in the domU.

Something like this caused a lot of confusion for folks around here:
they were expecting the _name_ used in the cfg to be the name in the
guest, ignoring the fact that neither hdX, xvdX nor sdX ever appear in a
Windows HVM.  Or indeed that, IDE, SCSI and SATA disks are all called
sdX nowadays.

As Stefan said, the name actually only tells you what sort of emulated
controller the disk is attached to: hd for IDE, sd for SCSI and xvd for
PV disks (no actual controller as such).    It might have been better to
have things like IDE(0,0), SCSI(0,3) and XVD(0) and let the guest OS
decide how to map those to names, much like it does for real hardware.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>