> -Original Message-
> From: Roger Pau Monne [mailto:roger@citrix.com]
> Sent: Wednesday, March 01, 2017 1:40 AM
> To: xen-de...@lists.xenproject.org
> Cc: Roger Pau Monne; Ian Jackson; Wei Liu; Elena Ufimtseva; Jan Beulich;
> Andrew Cooper;
> Paul Durrant; Nakajima, Jun; Tian,
On Tue, Feb 28, 2017 at 05:39:39PM +, Roger Pau Monne wrote:
> This removal applies to both the hypervisor and the toolstack side of PVHv1.
>
> Note that on the toolstack side there's one hiccup: on xl the "pvh"
> configuration option is translated to builder="hvm",
>
Roger Pau Monne writes ("Re: [PATCH v2 1/3] x86: remove PVHv1 code"):
> On Wed, Mar 01, 2017 at 02:51:33PM +, Ian Jackson wrote:
> > But config files are supposed to be written by nonprogrammers (or by
> > toolstack or orchestration system programmers).
>
> OK, I can be convinced that this is
On Wed, Mar 01, 2017 at 02:51:33PM +, Ian Jackson wrote:
> Roger Pau Monne writes ("Re: [PATCH v2 1/3] x86: remove PVHv1 code"):
> > It's not just the CPU extensions, we are also providing it with a
> > local APIC and ACPI tables,
>
> The host and guest system administrators do not care about
Roger Pau Monne writes ("Re: [PATCH v2 1/3] x86: remove PVHv1 code"):
> It's not just the CPU extensions, we are also providing it with a
> local APIC and ACPI tables,
The host and guest system administrators do not care about any of
that. These are implementation details.
> and it looks like
On Wed, Mar 01, 2017 at 02:18:16PM +, 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 +, Ian Jackson wrote:
> > > Well, PVHv2 is in the process of becoming properly supported, so now
> > > is the time to
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 +, Ian Jackson wrote:
>>> Well, PVHv2 is in the process of becoming properly supported, so now
>>> is the time to decide the "official" way.
>>
>>
On Wed, Mar 01, 2017 at 02:10:53PM +, Roger Pau Monne wrote:
> On Wed, Mar 01, 2017 at 01:53:29PM +, Ian Jackson wrote:
> > Roger Pau Monne writes ("Re: [PATCH v2 1/3] x86: remove PVHv1 code"):
> > > On Tue, Feb 28, 2017 at 05:44:51PM +, Ian Jackson wrote:
> > > > Are those explicit
Roger Pau Monne writes ("Re: [PATCH v2 1/3] x86: remove PVHv1 code"):
> On Wed, Mar 01, 2017 at 01:53:29PM +, 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"
On Wed, Mar 01, 2017 at 01:53:29PM +, Ian Jackson wrote:
> Roger Pau Monne writes ("Re: [PATCH v2 1/3] x86: remove PVHv1 code"):
> > On Tue, Feb 28, 2017 at 05:44:51PM +, Ian Jackson wrote:
> > > Are those explicit settings even a supported way to create a PVHv2
> > > domain ? I think
Roger Pau Monne writes ("Re: [PATCH v2 1/3] x86: remove PVHv1 code"):
> On Tue, Feb 28, 2017 at 05:44:51PM +, Ian Jackson wrote:
> > Are those explicit settings even a supported way to create a PVHv2
> > domain ? I think they probably shouldn't be.
>
> Those are the only ways to create a
> -Original Message-
> From: Roger Pau Monne [mailto:roger@citrix.com]
> Sent: 28 February 2017 17:40
> To: xen-de...@lists.xenproject.org
> Cc: Roger Pau Monne ; Ian Jackson
> ; Wei Liu ; Elena Ufimtseva
>
On 28/02/17 17:39, Roger Pau Monne wrote:
> This removal applies to both the hypervisor and the toolstack side of PVHv1.
>
> Note that on the toolstack side there's one hiccup: on xl the "pvh"
> configuration option is translated to builder="hvm",
> device_model_version="none". This is done
On Tue, Feb 28, 2017 at 05:44:51PM +, Ian Jackson wrote:
> Roger Pau Monne writes ("[PATCH v2 1/3] x86: remove PVHv1 code"):
> > This removal applies to both the hypervisor and the toolstack side of PVHv1.
> >
> > Note that on the toolstack side there's one hiccup: on xl the "pvh"
> >
On 28/02/17 17:39, Roger Pau Monne wrote:
> This removal applies to both the hypervisor and the toolstack side of PVHv1.
>
>
>
> 40 files changed, 96 insertions(+), 696 deletions(-)
What a diffstat, and so many fixeme's fixed.
Reviewed-by: Andrew Cooper
On Tue, Feb 28, 2017 at 05:44:51PM +, Ian Jackson wrote:
> Roger Pau Monne writes ("[PATCH v2 1/3] x86: remove PVHv1 code"):
> > This removal applies to both the hypervisor and the toolstack side of PVHv1.
> >
> > Note that on the toolstack side there's one hiccup: on xl the "pvh"
> >
On Tue, Feb 28, 2017 at 05:39:39PM +, Roger Pau Monne wrote:
> This removal applies to both the hypervisor and the toolstack side of PVHv1.
>
> Note that on the toolstack side there's one hiccup: on xl the "pvh"
> configuration option is translated to builder="hvm",
>
Roger Pau Monne writes ("[PATCH v2 1/3] x86: remove PVHv1 code"):
> This removal applies to both the hypervisor and the toolstack side of PVHv1.
>
> Note that on the toolstack side there's one hiccup: on xl the "pvh"
> configuration option is translated to builder="hvm",
>
This removal applies to both the hypervisor and the toolstack side of PVHv1.
Note that on the toolstack side there's one hiccup: on xl the "pvh"
configuration option is translated to builder="hvm",
device_model_version="none". This is done because otherwise xl would start
parsing PV like
19 matches
Mail list logo