Comment # 6 on bug 1209727 from Larry Finger

(In reply to Takashi Iwai from comment #4)
> Which kernel is in question?  I see no CONFIG_PROVE_LOCKING changes in our
> kernels at all.

According to the logging from openQA, the kernel in question is
6.2.8-1-default #1 openSUSE Tumbleweed 3fa4abf6558707e35b8fd19fc1aa28b27d42fa

When I run 6.2.8-1-default from the TW repos, VirtualBox works correctly with
no errors.

I have determined that the problems with CONFIG_PROVE_LOCKING are present in
VirtualBox 6.1.42, and predate our recent changes in the locking that were
needed to improve long-term stability on hosts with many processors and many
guests where the graphics was broken, but the underlying guest OS could still
be accessed via SSH.

I see that the test in question was started with QEMU. Has it or KVM been
changed resently?