From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Olaf Hering <olaf@aepfle.de>, xen-devel@lists.xen.org
Subject: Re: pvops xen_blkfront does not enforce device names
Date: Fri, 29 Apr 2016 10:39:33 +0100 [thread overview]
Message-ID: <57232BD5.6080701@citrix.com> (raw)
In-Reply-To: <5723296D02000078000E7144@prv-mh.provo.novell.com>
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.
David
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-29 9:39 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 [this message]
2016-04-29 10:43 ` Andrew Cooper
2016-04-29 11:27 ` Olaf Hering
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=57232BD5.6080701@citrix.com \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=olaf@aepfle.de \
--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).