Re: pvops xen_blkfront does not enforce device names

[Andrew Cooper <andrew.cooper3@citrix.com>]

On 29/04/16 10:39, David Vrabel wrote:
> On 29/04/16 08:29, 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?
> XenServer always named its PV disks as xvda etc.

The toolstack has no business trying to control how the guest chooses to
name its block devices.  The device name is private information to the
guest.

It should continue to function in exactly the same way even if the guest
admin edits their udev rules to rename it to something crazy like "&&&&".

~Andrew

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