From: Paolo Bonzini <pbonzini@redhat.com>
To: Stoiko Ivanov <s.ivanov@proxmox.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, bgardon@google.com
Subject: Re: [PATCH] KVM: x86: enable TDP MMU by default
Date: Tue, 26 Jul 2022 17:43:27 +0200 [thread overview]
Message-ID: <ffc99463-6a61-8694-6a4e-3162580f94ee@redhat.com> (raw)
In-Reply-To: <20220726165748.76db5284@rosa.proxmox.com>
On 7/26/22 16:57, Stoiko Ivanov wrote:
> Hi,
>
> Proxmox[0] recently switched to the 5.15 kernel series (based on the one
> for Ubuntu 22.04), which includes this commit.
> While it's working well on most installations, we have a few users who
> reported that some of their guests shutdown with
> `KVM: entry failed, hardware error 0x80000021` being logged under certain
> conditions and environments[1]:
> * The issue is not deterministically reproducible, and only happens
> eventually with certain loads (e.g. we have only one system in our
> office which exhibits the issue - and this only by repeatedly installing
> Windows 2k22 ~ one out of 10 installs will cause the guest-crash)
> * While most reports are referring to (newer) Windows guests, some users
> run into the issue with Linux VMs as well
> * The affected systems are from a quite wide range - our affected machine
> is an old IvyBridge Xeon with outdated BIOS (an equivalent system with
> the latest available BIOS is not affected), but we have
> reports of all kind of Intel CPUs (up to an i5-12400). It seems AMD CPUs
> are not affected.
>
> Disabling tdp_mmu seems to mitigate the issue, but I still thought you
> might want to know that in some cases tdp_mmu causes problems, or that you
> even might have an idea of how to fix the issue without explicitly
> disabling tdp_mmu?
If you don't need secure boot, you can try disabling SMM. It should not
be related to TDP MMU, but the logs (thanks!) point at an SMM entry (RIP
= 0x8000, CS base=0x7ffc2000).
This is likely to be fixed by
https://lore.kernel.org/kvm/20220621150902.46126-1-mlevitsk@redhat.com/.
Paolo
next prev parent reply other threads:[~2022-07-26 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 16:31 [PATCH] KVM: x86: enable TDP MMU by default Paolo Bonzini
2021-07-26 16:53 ` Ben Gardon
2022-07-26 14:57 ` Stoiko Ivanov
2022-07-26 15:43 ` Paolo Bonzini [this message]
2022-07-27 10:22 ` Maxim Levitsky
2022-07-27 13:31 ` Stoiko Ivanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ffc99463-6a61-8694-6a4e-3162580f94ee@redhat.com \
--to=pbonzini@redhat.com \
--cc=bgardon@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.ivanov@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).