Re: pvops xen_blkfront does not enforce device names

[Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>]

On Fri, Apr 29, 2016 at 01:29:17AM -0600, Jan Beulich wrote:
> >>> On 29.04.16 at 08:45, <konrad.wilk@oracle.com> wrote:
> > On Tue, Apr 26, 2016 at 03:28:45PM +0200, Olaf Hering wrote:
> >> Why does xen_blkfront not enforce kernel device names from domU.cfg?
> >> In my PV domU.cfg I still have something like this:
> >> disk=[ 'file:/path,hda,w' ]
> >> 
> >> With pvops and xen_blkfront I get xvda.
> >> With xenlinux and xenblk I get hda.
> > 
> > It has no business subverting the hda device names which
> > are specifically for legacy devices.
> 
> That's one view. The other is that people moving from XenoLinux to
> pv-ops are in trouble without it. How did you (or Citrix, if anyone of
> them looks) deal with this when doing the transition?

We had transition folks to use 'UUID' or volume group names in their 'root='
entry so never had an issue with this.
> 
> > [We got smacked down at some point for having done this]
> 
> In which way?

For usurping the 'hda'. Stefano may remember the details more..
> 
> Jan
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel