From: George Dunlap <george.dunlap@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>,
Roger Pau Monne <roger.pau@citrix.com>
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>,
Kevin Tian <kevin.tian@intel.com>,
Tamas K Lengyel <tamas@tklengyel.com>,
Wei Liu <wei.liu2@citrix.com>,
Jun Nakajima <jun.nakajima@intel.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Paul Durrant <paul.durrant@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 1/3] x86: remove PVHv1 code
Date: Wed, 1 Mar 2017 14:20:13 +0000 [thread overview]
Message-ID: <2e4b54c7-025c-7ae5-f2cb-a9a03b51f362@citrix.com> (raw)
In-Reply-To: <22710.55336.494328.893677@mariner.uk.xensource.com>
On 01/03/17 14:18, Ian Jackson wrote:
> Roger Pau Monne writes ("Re: [PATCH v2 1/3] x86: remove PVHv1 code"):
>> On Wed, Mar 01, 2017 at 01:53:29PM +0000, Ian Jackson wrote:
>>> Well, PVHv2 is in the process of becoming properly supported, so now
>>> is the time to decide the "official" way.
>>
>> I prefer builder="hvm" device_model_version="none" because I think
>> it's clearer from a user PoV that a HVM guest it being
>> created.
>
> Err, but a PVH guest is not an HVM guest in the sense that the user
> will expect. Whenever I explain to anyone the difference between PV
> and HVM, the explanation is that "HVM provides a complete emulated PC"
> and "PV needs a guest operating systemn modified to work under Xen".
> By both these measures, a PVH guest is more like PV than HVM.
>
> The use of the CPU extensions which originally only enabled support
> for HVM is a detail which most people will not be so interested in.
> The details of API, ABI and so on are not of interest to the writer of
> the xl domain config file.
>
>> OTOH, using pvh=1 it's more obscure, and it isn't clear
>> which kind of guest you are creating, and which options apply to
>> it. Although all that can be fixed in the man page, I think it's
>> less intuitive.
>
> The explanation we have been giving to ordinary users is that there
> are going to be three kinds of guest: PV, HVM, and the new PVH.
I was in the middle of writing something very similar to the above two
paragraphs, but instead I'll just say that I agree with Ian. :-)
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-01 14:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 17:39 [PATCH v2 0/3] x86: remove PVHv1 Roger Pau Monne
2017-02-28 17:39 ` [PATCH v2 1/3] x86: remove PVHv1 code Roger Pau Monne
2017-02-28 17:44 ` Ian Jackson
2017-02-28 17:51 ` Roger Pau Monne
2017-03-01 13:53 ` Ian Jackson
2017-03-01 14:10 ` Roger Pau Monne
2017-03-01 14:18 ` Ian Jackson
2017-03-01 14:20 ` George Dunlap [this message]
2017-03-01 14:32 ` Roger Pau Monne
2017-03-01 14:51 ` Ian Jackson
2017-03-01 15:24 ` Roger Pau Monne
2017-03-01 15:30 ` Ian Jackson
2017-03-01 14:18 ` Roger Pau Monne
2017-03-01 12:07 ` Wei Liu
2017-02-28 17:47 ` Wei Liu
2017-02-28 18:05 ` Andrew Cooper
2017-03-01 12:35 ` George Dunlap
2017-03-01 13:20 ` Paul Durrant
2017-03-01 16:03 ` Elena Ufimtseva
2017-03-02 6:25 ` Tian, Kevin
2017-02-28 17:39 ` [PATCH v2 2/3] x86: remove has_hvm_container_{domain/vcpu} Roger Pau Monne
2017-02-28 17:52 ` Boris Ostrovsky
2017-03-01 12:36 ` George Dunlap
2017-02-28 17:39 ` [PATCH v2 3/3] x86/PVHv2: move pvh_setup_e820 together with the other pvh functions Roger Pau Monne
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=2e4b54c7-025c-7ae5-f2cb-a9a03b51f362@citrix.com \
--to=george.dunlap@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=elena.ufimtseva@oracle.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=paul.durrant@citrix.com \
--cc=rcojocaru@bitdefender.com \
--cc=roger.pau@citrix.com \
--cc=tamas@tklengyel.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.