From: Wei Liu <wei.liu2@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Anthony Perard <anthony.perard@citrix.com>,
Wei Liu <Wei.Liu2@citrix.com>,
George Dunlap <george.dunlap@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: Thu, 2 Jun 2016 12:49:16 +0100 [thread overview]
Message-ID: <20160602114916.GV5160@citrix.com> (raw)
In-Reply-To: <20160601214051.GA28165@aepfle.de>
On Wed, Jun 01, 2016 at 11:40:51PM +0200, Olaf Hering wrote:
> On Wed, Jun 01, Olaf Hering wrote:
>
> > 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:
>
> Actually the list goes like shown below after some real testing.
> Now sure why xvd/qemu-xen/raw|qcow2 fails with our 4.5.2 based dom0.
> In the end the regression remains in xvd+qemu-xen.
>
> tool_ver vdev_str qemu format usable bootable
> xen-4.5 xvd qtrad raw yes no
> xen-4.5 xvd qtrad qcow2 no -
> xen-4.5 xvd qmain raw yes SUSE:no, staging:yes
> xen-4.5 xvd qmain qcow2 yes SUSE:no, staging:yes
What does "staging" mean?
> xen-4.5 hd qtrad raw yes yes
> xen-4.5 hd qtrad qcow2 no -
> xen-4.5 hd qmain raw yes yes
> xen-4.5 hd qmain qcow2 yes yes
>
>
> xen-4.6 xvd qtrad raw yes no
> xen-4.6 xvd qtrad qcow2 no -
> xen-4.6 xvd qmain raw yes yes
> xen-4.6 xvd qmain qcow2 yes yes
> xen-4.6 hd qtrad raw yes yes
> xen-4.6 hd qtrad qcow2 no -
> xen-4.6 hd qmain raw yes yes
> xen-4.6 hd qmain qcow2 yes yes
>
>
> xen-4.7 xvd qtrad raw yes no
> xen-4.7 xvd qtrad qcow2 no -
> xen-4.7 xvd qmain raw yes no
> xen-4.7 xvd qmain qcow2 yes no
> xen-4.7 hd qtrad raw yes yes
> xen-4.7 hd qtrad qcow2 no -
> xen-4.7 hd qmain raw yes yes
> xen-4.7 hd qmain qcow2 yes yes
>
So the last column only apply to xenlinux kernel?
I expect pvops to be all "yes" because it doesn't use vdev_str. I also
expect freebsd to work because it parses vbd number and translates that
to freebsd-speak device identifier.
Wei.
> Olaf
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-02 11:49 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
2016-06-01 21:40 ` Olaf Hering
2016-06-02 11:49 ` Wei Liu [this message]
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=20160602114916.GV5160@citrix.com \
--to=wei.liu2@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=george.dunlap@citrix.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).