From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
Olaf Hering <olaf@aepfle.de>, 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, 8 Jun 2016 11:17:26 +0100 [thread overview]
Message-ID: <22359.61622.670391.539650@mariner.uk.xensource.com> (raw)
In-Reply-To: <5756D546.9000609@citrix.com>
George Dunlap writes ("Re: [Xen-devel] 4.7 qemu regression: HVM guests fail to boot from xvda"):
> In every part of the whole system -- in dom0, in the guest, in
> everything -- I use xvda; *except* in the parts dealing with the guest
> config, where for some reason I mysteriously put 'hda', which ends up
> producing an xvda either when booted PV or when booted HVM. Does that
> make any sense?
>
> What about a per-disk property, emulate={default,always,only}, which for
> HVM will do the things we're talking about and be ignored on PV?
> 'default' will behave as it does now: xvda will get you only PV, hda
> will get you PV-backed emulated. 'always' will always give you an
> emulated device even if you specify xvda, and 'only' will only give you
> an emulated device (with no PV).
This is one of my suggestions which Olaf didn't like.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-08 10: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
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 [this message]
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=22359.61622.670391.539650@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=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).