[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] pvops xen_blkfront does not enforce device names

On Fri, Apr 29, Konrad Rzeszutek Wilk 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.

Old IDE drives are not SCSI either, but now they appear as 'sd' since a

'hd' or 'sd' or 'mmc' or 'xvd' are just names. They do not represent
hardware as such. Otherwise the interface into the blocklayer to request
major/minor/name would be like 'hey, I'm the IDE/SCSI/MMC/whatever
driver, give me something'.

Anyway, since this is now set in stone, any VM out there which still is
configured to use /dev/hd* has to be adjusted to /dev/xvd* upfront when
going from xenlinux to pvops.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.