From: Olaf Hering <olaf@aepfle.de>
To: George Dunlap <george.dunlap@citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
Wei Liu <Wei.Liu2@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: 4.7 qemu regression: HVM guests fail to boot from xvda
Date: Wed, 1 Jun 2016 15:17:08 +0200 [thread overview]
Message-ID: <20160601131708.GA6297@aepfle.de> (raw)
In-Reply-To: <20160531120447.GA24706@aepfle.de>
On Tue, May 31, Olaf Hering wrote:
> On Tue, May 31, George Dunlap wrote:
>
> > Do you have a concrete proposal?
>
> I have to give it some more thought what the impact really is, what
> config variants are affected.
Here is a list. Essentially it means that upgrading dom0 to xen-4.7
might break existing domU if they happen to use xvd* in domU.cfg:
device names which the emulated BIOS can boot from:
num tool_ver vdev_str bootable
01 xen-4.2 hd yes
02 xen-4.2 xvd no
03 xen-4.3 hd yes
04 xen-4.3 xvd yes
05 xen-4.4 hd yes
06 xen-4.4 xvd yes
07 xen-4.5 hd yes
08 xen-4.5 xvd yes
09 xen-4.6 hd yes
10 xen-4.6 xvd yes
11 xen-4.7-rc hd yes
12 xen-4.7-rc xvd no
block frontend drivers which will use the vdev_str:
a) pvops no (defaults to xvd)
b) xenlinux yes
c) solaris ??? (Konrad suggests yes)
d) bsd ???
e) windows ??? (likely no due to drive letters)
domU.cfg configuration which will break with xen-4.7:
04|06|08|10 -> 12
after adjusting to 11 to allow boot again:
b + 11
In real life this means existing SLE11/SLE12/openSUSE domU with
vdev_str==xvd when dom0 is upgraded to xen-4.7, and the domU makes use
of kernel device names.
Olaf
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-01 13:17 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 20:42 4.7 qemu regression: HVM guests fail to boot from xvda Olaf Hering
2016-05-31 11:02 ` George Dunlap
2016-05-31 11:16 ` Olaf Hering
2016-05-31 11:32 ` George Dunlap
2016-05-31 11:41 ` Olaf Hering
2016-05-31 12:00 ` George Dunlap
2016-05-31 12:04 ` Olaf Hering
2016-06-01 13:17 ` Olaf Hering [this message]
2016-06-01 21:40 ` Olaf Hering
2016-06-02 11:49 ` Wei Liu
2016-06-02 12:06 ` Olaf Hering
2016-05-31 12:15 ` Jan Beulich
2016-06-01 9:48 ` Wei Liu
2016-06-01 13:34 ` Olaf Hering
2016-06-01 14:11 ` Wei Liu
2016-06-01 14:32 ` Olaf Hering
2016-06-01 15:36 ` Ian Jackson
2016-06-03 10:13 ` George Dunlap
2016-06-03 11:20 ` Olaf Hering
2016-06-03 11:27 ` George Dunlap
2016-06-03 11:45 ` Ian Jackson
2016-06-06 10:39 ` George Dunlap
2016-06-06 10:52 ` Ian Jackson
2016-06-06 11:43 ` George Dunlap
2016-06-06 12:49 ` George Dunlap
2016-06-07 14:08 ` George Dunlap
2016-06-07 14:27 ` Olaf Hering
2016-06-08 10:17 ` Ian Jackson
2016-06-07 19:06 ` Olaf Hering
2016-06-08 10:18 ` Ian Jackson
2016-06-08 10:23 ` George Dunlap
2016-06-08 10:30 ` Ian Jackson
2016-06-08 10:49 ` George Dunlap
2016-06-08 11:13 ` Olaf Hering
2016-06-08 15:56 ` Konrad Rzeszutek Wilk
2016-06-03 11:50 ` Olaf Hering
2016-05-31 12:10 ` Jan Beulich
2016-05-31 13:41 ` George Dunlap
2016-05-31 14:10 ` Jan Beulich
2016-05-31 16:15 ` Konrad Rzeszutek Wilk
2016-06-08 11:38 ` Wei Liu
2016-06-08 12:04 ` Olaf Hering
2016-06-08 12:09 ` Wei Liu
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=20160601131708.GA6297@aepfle.de \
--to=olaf@aepfle.de \
--cc=Wei.Liu2@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=george.dunlap@citrix.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).