Re: [Qemu-devel] [PATCH 2/2] WHPX: register for unrecognized MSR exits

2018-06-19 Thread Paolo Bonzini
On 19/06/2018 00:01, Justin Terry (VM) wrote: > The issue is that the Windows Hypervisor Platform will return #GP for > any rdmsr/wrmsr that is not a virtualized MSR in the hypervisor by > default. A virt stack (QEMU) can override this default behavior by > registering for MSR exits. In this

Re: [Qemu-devel] [PATCH 2/2] WHPX: register for unrecognized MSR exits

2018-06-18 Thread Justin Terry (VM) via Qemu-devel
Hey Paolo, Thanks for the reply. I am certainly open for suggestions if you have any here. This was originally reported when running the android kernel which I believe is Linux 4.4. I agree that newer kernels do seem to handle #GP more gracefully than others but it doesn’t help down level

Re: [Qemu-devel] [PATCH 2/2] WHPX: register for unrecognized MSR exits

2018-06-13 Thread Paolo Bonzini
On 06/06/2018 00:15, Justin Terry (VM) wrote: > Some variations of Linux kernels end up accessing MSR's that the Windows > Hypervisor doesn't implement which causes a GP to be returned to the guest. > This fix registers QEMU for unimplemented MSR access and globally returns 0 on > reads and

[Qemu-devel] [PATCH 2/2] WHPX: register for unrecognized MSR exits

2018-06-05 Thread Justin Terry (VM) via Qemu-devel
Some variations of Linux kernels end up accessing MSR's that the Windows Hypervisor doesn't implement which causes a GP to be returned to the guest. This fix registers QEMU for unimplemented MSR access and globally returns 0 on reads and ignores writes. This behavior is allows the Linux kernel to