* Virtual LAPIC page corruption
@ 2020-05-13 4:21 Suresh Gumpula
2020-05-14 15:21 ` Suresh Gumpula
0 siblings, 1 reply; 2+ messages in thread
From: Suresh Gumpula @ 2020-05-13 4:21 UTC (permalink / raw)
To: kvm, linux-kernel
Hi,
We are a seeing a problem with windows guests(2016/2012R2) where guest crashes with
Virtual APIC page corruption similar to the following redhat ticket.
https://bugzilla.redhat.com/show_bug.cgi?id=1751017
> Arg4: 0000000000000017, Type of corrupted region, can be
16 : Critical floating point control register modification
17 : Local APIC modification
Here, we are seeing the corruption LAPIC page and guest is BSOD'ing.
Looking at the guest windows dump, we see the full page is zeroed. And it seems the
Guest windows kernel patchguard is detecting this case and resetting the VM.
Is it possible that KVM, somehow corrupted the virtual LAPIC page? While the guest is running
the KVM is not supposed to touch that vcpu lapic page?
Could you please give us some pointers on what could wrong here. Is it a known issue in the kvm?
We are using the host kernel 4.19 and qemu 2.12 and windows guests(2016/2012)
Thanks,
Suresh
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Virtual LAPIC page corruption
2020-05-13 4:21 Virtual LAPIC page corruption Suresh Gumpula
@ 2020-05-14 15:21 ` Suresh Gumpula
0 siblings, 0 replies; 2+ messages in thread
From: Suresh Gumpula @ 2020-05-14 15:21 UTC (permalink / raw)
To: kvm, linux-kernel
Appears this also can be reproduced with 5.4 kernel too.
And from windows debugger dump, arg3 the LVTT 0x320 seems corrupted
and the patchguard complaining. But also from the dump full lapic 4k page is 0, not just 0x320 offset.
Thanks,
Suresh
On 5/12/20, 9:21 PM, "kvm-owner@vger.kernel.org on behalf of Suresh Gumpula" <kvm-owner@vger.kernel.org on behalf of suresh.gumpula@nutanix.com> wrote:
Hi,
We are a seeing a problem with windows guests(2016/2012R2) where guest crashes with
Virtual APIC page corruption similar to the following redhat ticket.
https://urldefense.proofpoint.com/v2/url?u=https-3A__bugzilla.redhat.com_show-5Fbug.cgi-3Fid-3D1751017&d=DwIGaQ&c=s883GpUCOChKOHiocYtGcg&r=nwda3lAP7hp57HFC_RJglj6ciwz98d-U4grSzoi79ms&m=JmF-BAGwMBgFp2S9HWvbSsqMj8rJSO_dyYSzImngOYc&s=m9NzlXWIWtaKstvIZLZDESPhfve_xGYWjSF_AWf9CQQ&e=
> Arg4: 0000000000000017, Type of corrupted region, can be
16 : Critical floating point control register modification
17 : Local APIC modification
Here, we are seeing the corruption LAPIC page and guest is BSOD'ing.
Looking at the guest windows dump, we see the full page is zeroed. And it seems the
Guest windows kernel patchguard is detecting this case and resetting the VM.
Is it possible that KVM, somehow corrupted the virtual LAPIC page? While the guest is running
the KVM is not supposed to touch that vcpu lapic page?
Could you please give us some pointers on what could wrong here. Is it a known issue in the kvm?
We are using the host kernel 4.19 and qemu 2.12 and windows guests(2016/2012)
Thanks,
Suresh
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-05-14 15:21 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-05-13 4:21 Virtual LAPIC page corruption Suresh Gumpula
2020-05-14 15:21 ` Suresh Gumpula
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).