From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Haxby Subject: Re: Re: Question on "xen-blkfront: handle Xen major numbers other than XENVBD" Date: Wed, 13 Jul 2011 18:25:21 +0100 Message-ID: <4E1DD501.7030503@oracle.com> References: <4E1D6A48.1020801@canonical.com> <1310554481.634.381.camel@zakaz.uk.xensource.com> <4E1D8C1C.1040200@canonical.com> <4E1DA16E.6020302@canonical.com> <4E1DC57D.3010002@canonical.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4E1DC57D.3010002@canonical.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefan Bader Cc: "xen-devel@lists.xensource.com" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org 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. jch