After updated from linux-image-5.14.0-1042-oem VirtualBox VMs started crashing

[Christian Connert]

With kernel linux-image-5.14.0-1042-oem VirtualBox VM runs stable
With kernel linux-image-5.14.0-1044-oem VirtualBox VM crashed constantly
Wiht kernel linux-image-5.14.0-1045-oem VirtualBox VM crash multiple times a day

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.14.0-1045-oem 5.14.0-1045.51
ProcVersionSignature: Ubuntu 5.14.0-1045.51-oem 5.14.21
Uname: Linux 5.14.0-1045-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Thu Jul 14 09:15:24 2022
InstallationDate: Installed on 2021-07-22 (356 days ago)
InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
SourcePackage: linux-signed-oem-5.14
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jeff Dairiki (dairiki)]

Me too.

After the upgrade to:
  linux-image-5.14.0-1044-oem
and continuing with
  linux-image-5.14.0-1045-oem
the one VirtualBox VM (Windows 10) that I run has started throwing various BSODs.

I tried a fresh Windows 10 install in a new VM (several times) under linux-image-5.14.0-1045-oem.
Typically, it seems okay for a while, but the install never ran to completion before reporting some sort of error and stopping.

I just booted into
  linux-image-5.15.0-41-generic
and my original VM seems to run stably there. (Fresh installs of Window 10 into a new VM seem to work, too.)

If I can help diagnose further, let me know how.

[Joerg Schmauder (schmauder)]

i can confirm the bug. things i tried that did not help:

- reducing guest CPUs to 1
- turning off hardware acceleration for the guest VM
- setting kernel parameter "split_lock_detect=off"

with kernel 5.15.0-41-generic no VM crashes (windows 10) so far.

[Christian Connert (chri-connert)]

Today I installed the latest Virtualbox: 3.1.36r152435. So I figured I give it a try and the Windows VM is running stable since 1,5 h on 5.14.0-1045-oem.
If it keeps running for the rest of today, I'll give it a full day test tomorrow and report back.

[Christian Connert (chri-connert)]

My VM has been running solid for 8h today. So it seems my issue got resolved

[Christian Connert (chri-connert)]

Looking at the changelog (https://www.virtualbox.org/wiki/Changelog) I have no clue what could have fixed the issue