From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: 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: Tue, 31 May 2016 12:15:23 -0400 [thread overview]
Message-ID: <20160531161523.GB21835@char.us.oracle.com> (raw)
In-Reply-To: <20160531111614.GA13143@aepfle.de>
On Tue, May 31, 2016 at 01:16:14PM +0200, Olaf Hering wrote:
> On Tue, May 31, George Dunlap wrote:
>
> > On Mon, May 30, 2016 at 9:42 PM, Olaf Hering <olaf@aepfle.de> wrote:
> > > With staging-4.6 this domU boots from xvda, qemu creates an emulated
> > > disk. With staging no disk is found, unless the name is changed to hda.
> > > Looks like qemu-2.6 does not handle xvda either.
> >
> > This was intentional; see this thread:
> >
> > https://marc.info/?i=<1444820717-25565-1-git-send-email-anthony.perard@citrix.com>
> >
> > The idea was to make it possible to create an HVM guest with no
> > emulated disks for guest booting with OVMF which contains PV drivers.
>
> This breaks the domU becasue it changes its device names from 'xvd' to
> 'hd' if a xenlinux based kernel is used in domU.
> In other words: every SUSE domU out there.
And every Solaris domU too.
>
> Olaf
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-31 16:15 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
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 [this message]
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=20160531161523.GB21835@char.us.oracle.com \
--to=konrad.wilk@oracle.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).