From: Olaf Hering <olaf@aepfle.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xen.org
Subject: Re: pvops xen_blkfront does not enforce device names
Date: Fri, 29 Apr 2016 13:27:35 +0200 [thread overview]
Message-ID: <20160429112735.GA9447@aepfle.de> (raw)
In-Reply-To: <20160429064502.GA11592@char.us.oracle.com>
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
while.
'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.
Olaf
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-29 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 13:28 pvops xen_blkfront does not enforce device names Olaf Hering
2016-04-29 6:45 ` Konrad Rzeszutek Wilk
2016-04-29 7:29 ` Jan Beulich
2016-04-29 7:34 ` Konrad Rzeszutek Wilk
2016-04-29 11:08 ` Stefano Stabellini
2016-04-29 9:39 ` David Vrabel
2016-04-29 10:43 ` Andrew Cooper
2016-04-29 11:27 ` Olaf Hering [this message]
2016-04-29 13:31 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160429112735.GA9447@aepfle.de \
--to=olaf@aepfle.de \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).