From: Sean Christopherson <seanjc@google.com>
To: "František Šumšal" <frantisek@sumsal.cz>
Cc: kvm@vger.kernel.org
Subject: Re: BUG: soft lockup - CPU#0 stuck for 26s! with nested KVM on 5.19.x
Date: Wed, 7 Sep 2022 15:08:14 +0000 [thread overview]
Message-ID: <Yxiz3giU/WEftPp6@google.com> (raw)
In-Reply-To: <a861d348-b3fd-fd1d-2427-0a89ae139948@sumsal.cz>
On Wed, Sep 07, 2022, František Šumšal wrote:
> Hello!
>
> In our Arch Linux part of the upstream systemd CI I recently noticed an
> uptrend in CPU soft lockups when running one of our tests. This test runs
> several systemd-nspawn containers in succession and sometimes the underlying
> VM locks up due to a CPU soft lockup
By "underlying VM", do you mean L1 or L2? Where
L0 == Bare Metal
L1 == Arch Linux (KVM, 5.19.5-arch1-1/5.19.7-arch1-1)
L2 == Arch Linux (nested KVM or QEMU TCG, 5.19.5-arch1-1/5.19.7-arch1-1)
> (just to clarify, the topology is: CentOS Stream 8 (baremetal,
> 4.18.0-305.3.1.el8) -> Arch Linux (KVM, 5.19.5-arch1-1/5.19.7-arch1-1) ->
> Arch Linux (nested KVM or QEMU TCG, happens with both,
> 5.19.5-arch1-1/5.19.7-arch1-1) -> nspawn containers).
Since this repros with TCG, that rules out nested KVM as the cuplrit.
> I did some further testing, and it reproduces even when the baremetal is my
> local Fedora 36 machine (5.17.12-300.fc36.x86_64).
>
> Unfortunately, I can't provide a simple and reliable reproducer, as I can
> reproduce it only with that particular test and not reliably (sometimes it's
> the first iteration, sometimes it takes an hour or more to reproduce).
> However, I'd be more than glad to collect more information from one such
> machine, if possible.
...
> Also, in one instance, the machine died with:
Probably unrelated, but same question as above: which layer does "the machine"
refer to?
next prev parent reply other threads:[~2022-09-07 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 9:39 BUG: soft lockup - CPU#0 stuck for 26s! with nested KVM on 5.19.x František Šumšal
2022-09-07 15:08 ` Sean Christopherson [this message]
2022-09-07 15:11 ` František Šumšal
2022-09-07 15:23 ` Sean Christopherson
2022-09-08 8:30 ` František Šumšal
2022-09-08 15:08 ` Sean Christopherson
2022-09-08 15:24 ` František Šumšal
2022-09-09 8:33 ` František Šumšal
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=Yxiz3giU/WEftPp6@google.com \
--to=seanjc@google.com \
--cc=frantisek@sumsal.cz \
--cc=kvm@vger.kernel.org \
/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