Hey Eduardo/Paolo,
I have not forgotten about your responses. I am working out how best to do this
in our platform and will send a follow up patch (this one is already merged) to
fully support the -cpu flag. It looks like all the pieces are in place between
the two and we just need a bit of
On Thu, Apr 05, 2018 at 05:50:20PM +0200, Paolo Bonzini wrote:
> On 28/03/2018 22:48, Justin Terry (VM) wrote:
[...]
> > If we use [2] to inject the answers at creation time WHPX needs access
> > to the CPUX86State at accel init which also doesn't seem to be possible
> > in QEMU today. WHPX could
On 28/03/2018 22:48, Justin Terry (VM) wrote:
> 1. (As the code is doing now). At partition creation time you can
> register for specific CPUID exits and then respond to the CPUID with
> your custom answer or with the Hypervisor defaults that were forwarded
> to you. Unfortunately, QEMU has no way
On Wed, Mar 28, 2018 at 08:48:54PM +, Justin Terry (VM) wrote:
> Hey Eduardo
>
> Responses inline. Thanks!
>
> > -Original Message-
> > From: Eduardo Habkost
> > Sent: Wednesday, March 28, 2018 10:51 AM
> > To: Justin Terry (VM)
> > Cc:
Hey Eduardo
Responses inline. Thanks!
> -Original Message-
> From: Eduardo Habkost
> Sent: Wednesday, March 28, 2018 10:51 AM
> To: Justin Terry (VM)
> Cc: qemu-devel@nongnu.org; pbonz...@redhat.com; r...@twiddle.net
> Subject: Re: [PATCH]
On Mon, Mar 26, 2018 at 10:06:58AM -0700, Justin Terry (VM) wrote:
> Implements the CPUID trap for CPUID 1 to include the
> CPUID_EXT_HYPERVISOR flag in the ECX results. This was preventing some
> older linux kernels from booting when trying to access MSR's that dont
> make sense when virtualized.
On 03/26/2018 12:06 PM, Justin Terry (VM) via Qemu-devel wrote:
[meta-comment]
Since we're already discussing this today, I noticed the list rewrites
your headers due to SPF policies at microsoft.com, to the point that a
blind 'git am' on the list message will attempt to attribute your patch
Implements the CPUID trap for CPUID 1 to include the
CPUID_EXT_HYPERVISOR flag in the ECX results. This was preventing some
older linux kernels from booting when trying to access MSR's that dont
make sense when virtualized.
Signed-off-by: Justin Terry (VM)
---