From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Bader <stefan.bader@canonical.com>
Subject: Question on "xen-blkfront: handle Xen major numbers
	other than XENVBD"
Date: Wed, 13 Jul 2011 11:50:00 +0200
Message-ID: <4E1D6A48.1020801@canonical.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

This is /me trying to understand the background of

commit c80a420995e721099906607b07c09a24543b31d9
Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Date:   Thu Dec 2 17:55:00 2010 +0000

    xen-blkfront: handle Xen major numbers other than XENVBD

My guess would be that it has its reason from running HVM guests. The issue I in
some way hear in complaints is, that running as PVM guest (at least) people seem
to have used for example "sda1" in the instance configuration and then relied on
the device being called that way within the instance. Now it is suddenly called
"xvde1".
This is maybe a broken assumption in the first place, and not that hard to cope
with (its just surprising and maybe breaks some automation). I mainly want to
understand the reasoning, so I can explain it where I get asked.

Thanks,
Stefan