Therefore all write attempts should produce #GP, just like on real
hardware.
Signed-off-by: Jan Beulich
--- a/xen/arch/x86/hvm/vmx/vmx.c
+++ b/xen/arch/x86/hvm/vmx/vmx.c
@@ -3138,10 +3138,7 @@ static int vmx_msr_write_intercept(unsig
break;
case MSR_INTEL_PLATFORM_INFO:
-
On Fri, Sep 22, 2017 at 03:07:44AM -0600, Jan Beulich wrote:
> Therefore all write attempts should produce #GP, just like on real
> hardware.
>
> Signed-off-by: Jan Beulich
>
> --- a/xen/arch/x86/hvm/vmx/vmx.c
> +++ b/xen/arch/x86/hvm/vmx/vmx.c
> @@ -3138,10 +3138,7 @@ static int vmx_msr_write_i
On 22/09/17 10:07, Jan Beulich wrote:
Therefore all write attempts should produce #GP, just like on real
hardware.
Signed-off-by: Jan Beulich
Sergey has already posted a patch series to fix this.
What is the benefit of this version? As far as I can tell, it isn't as
complete as his work, b
>>> On 22.09.17 at 19:05, wrote:
> On Fri, Sep 22, 2017 at 03:07:44AM -0600, Jan Beulich wrote:
>> Therefore all write attempts should produce #GP, just like on real
>> hardware.
>>
>> Signed-off-by: Jan Beulich
>>
>> --- a/xen/arch/x86/hvm/vmx/vmx.c
>> +++ b/xen/arch/x86/hvm/vmx/vmx.c
>> @@ -3
>>> On 22.09.17 at 19:38, wrote:
> On 22/09/17 10:07, Jan Beulich wrote:
>> Therefore all write attempts should produce #GP, just like on real
>> hardware.
>>
>> Signed-off-by: Jan Beulich
>
> Sergey has already posted a patch series to fix this.
>
> What is the benefit of this version? As far
