[SRU] VirtualBox 6.1.34 guests crash with kernel 5.15.0-47

This change was made by a bot.

I can confirm, this is a bug in the kernel 47. I have an AMD Ryzen 7 5800. In my case the Windows 10 boots up in VM, but when I execute any Chromium based browser inside the VM it crashes without an error message. After trying several times to execute the browser the guest system also crashes without BSOD, and restarts.

I can confirm this with a Kubuntu Guest on a Kubuntu Host (both 22.04.1)

Firefox will crash on average every 30 seconds, no matter what website you are on, the more you interact with it the faster it will crash.

Chromium will also crash occasionally, but far less often than Firefox.

Some other apps have also crashed occasionally in the last 2 days and even the entire plasma shell in the guest has crashed a few times, black screen or frozen and once it was not even possible to shut down the guest with ACPI event anymore.

Downgrading to the previous -46 kernel made all these problems disappear.

I am also impacted by this. I had already logged a bug against virtualbox:

https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1988460

Although, I can't really say if the problem is actually with the new kernel or with virtualbox.

Kernel I'd say.
Reproduced with host system Ubuntu 22.04 / 5.15.0-47.
Affected Mint as well as Ubuntu virtual boxes (64-bit).
Boxes do boot, but then desktop as well as firefox crashes regurlarly. Firefox as soon as graphical content is displayed on a page, I feel.
Firefox throwing:
VA-API test failed: failed to initialise VAAPI connection.

I can confirm this bug as well. It actually also affects Ubuntu VMs and all other types of virtual machines withing Virtualbox.

I can confirm this bug as well. When I using Linux Mint with kernel 5.15.0-47 other Ubuntu and Mint machines will crash. I get back kernel 5.15.0-46 and anything works well. Virtualbox Version 6.1.34_Ubuntu r150636

I had created a question on askubuntu about the same issue: https://askubuntu.com/questions/1426992/22-04-jammy-is-there-a-kernel-bug-that-causes-virtualbox-to-misbehave-with-5-15/1427135

My system details:

Ubuntu 22.04.1 LTS x86_64
HP EliteDesk 805 G6 Desktop Mini PC
AMD Ryzen 5 PRO 4650G with Radeon Graphics (12) @ 4.308GHz

Updating to the latest VirtualBox version (6.1.34 -> 6.1.38 r153438) solved the problem for me on Xubuntu (with a running 5.15.0-47 kernel). https://www.virtualbox.org/wiki/Linux_Downloads

A more generic title for the bug might be something like "VirtualBox 6.1.34 breaks VMs after kernel 5.15.0-47 update" as the guest VMs are not limited to Windows.

VM mozilla application crash feedback data

I'm experiencing the same problem.

As a host OS I'm running an up to date Ubuntu 22.04.1 LTS x86_64 with kernel 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64.

I'm using the latest VirtualBox from the Ubuntu 22.04 package repository: 6.1.34-dfsg-3~ubuntu1.22.04.1

The host OS is stable.

In VirtualBox I'm running a number of guest Ubuntu 22.04 virtual machines. These all crash in some way or other every 30 seconds or so. Generally the guest's Gnome display manager crashes, the guest's desktop disappears and the guest's GUI applications terminate. I'm then returned to the guest's Gnome graphical login prompt, but at a lower resolution than normal.

For me this started occurring on the 2nd September 2022.

System: AMD Ryzen 5 3600 with NVIDIA GeForce GTX 1050 Ti

This debian bug might be related:

VirtualBox 6.1.34 not compatible with with Debian Kernel 5.18.0 and result in crashes - Patch available
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012627

changing package to virtualbox, as hints lead there

I am experiencing the same problem with linux 5.15.0-47 and VirtualBox 6.1.34-dfsg-3~ubuntu1.22.04.1:
Several VMs (guest OSes: Linux, FreeBSD, OpenBSD, Hurd) show malfunctions:
  - compiler crashes with internal compiler error,
  - assembler crashes,
  - sh report malloc/free mismatches,
  - gnome-shell crashes,
  - Hurd file system gets damaged.
The malfunctions are especially frequent when the system is loaded (top shows
a load larger than 2).

I changed the config of 2 VMs to reduce hardware virtualization:
- System > Motherboard > Extended Features > I/O APIC: Disable
- System > Acceleration > Paravirtualization Interface: Default -> None
- System > Acceleration > Hardware Virtualization > Enable Nested Paging: Disable
and let the two VMs run at full power at the same time. It was still unstable.

After downgrading to linux 5.15.0-46 — keeping the same VirtualBox version —,
I can again run 6 VMs in parallel, doing compilations at full power, and everything is fine.

System: AMD Ryzen 7 4800U with Radeon Graphics

Recipe for downgrading:
  # apt install linux-image-5.15.0-46-generic:amd64 linux-headers-5.15.0-46-generic:amd64 linux-modules-5.15.0-46-generic:amd64 linux-headers-5.15.0-46:amd64 linux-modules-extra-5.15.0-46-generic:amd64
Then modify /etc/default/grub, setting
  GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 5.15.0-46-generic"
and run
  # update-grub

I was affected too. Programs running in the guest were facing severe instability (crashing with SIGSEGV etc). Switching to VirtualBox downloaded from virtualbox.org fixed it for me.

I have absolutely no problems, that depends on the Linux release. If have all kinds of VMs running 4.15 till 5.19 and all work fine with Virtualbox 6.1.36. I have no problem with any of the flavors or remixes of 22.04 LTS nor with 20.04 LTS. I only have a problem with Ubuntu 22.10 development edition and that one runs 5.15.0-27 an old version of 5.15. It even freezes, if I run the pre-release option with Linux 5.19.

If I roll back 22.10 to an older version from approx 2 weeks ago, the 22.10 system works with Linux 5.15.0-27 and Virtualbox 6.1.36. I also tried an older version 6.1.18 of Virtualbox Guest Additions and the system did freeze again. So my problem has nothing to do with Virtualbox 6.1.36 nor with Linux 5.15.0.27 or any other Linux version.

The system freezes at the moment it calls the Gnome display manager for the login screen. It is 100% reproducible and it even happens after a fresh install of the VM. It started to occur after an update of the 22.10 Desktop, NOT after an update of Linux NOR after an update of Virtualbox.

I have the unhappy feeling that we are starting to mix different reports with different problems. So I propose to keep my Bug 1988488 separate.

Hello, I'm upgrading to 6.1.38 right now, I'll sync tomorrow to Ubuntu kinetic (22.10) and then SRU this version to 20.04 and 22.04.
I'll ask for testing once its accepted.

Similar problem to many here. I recently updated my 22.04 installation to kernel 5.15.0-47 . After that, any software I had running in either of two different linux guest OS's (Bodhi, ubuntu mate) became highly unstable, particularly when they utilized media streams / active content.

Upgrading to VirtualBox 6.1.38 evidently solved the problem. However, upgrading to 6.1.38 was a time-consuming mess as I describe here: https://forums.virtualbox.org/viewtopic.php?f=7&t=107000&p=523536#p523536 There are some tricks to successfully upgrading that I describe there. One of the problems is that installation through the Ubuntu package system did not work for me (keeps running into errors).

I upgraded the following VMs from 6.1.36 to 6.1.38. I had no problems with 6.1.36 and I had no problems with 6.1.38.
Xubuntu 22.04 LTS
Ubuntu 16.04 Extended Security Maintenance
Ubuntu Studio 20.04 LTS
Ubuntu 22.04 LTS
Windows XP Home
Windows 11 Pro
All updates went smoothly and I never had any problems with these system during this year!

I updated my ~17 days old version of Ubuntu 22.10 to Virtualbox 6.1.38 and that 17 days old version worked fine with both Virtualbox 6.1.36 and 6.1.38 both using Linux 5.15.0-27.
After I did a partial upgrade of Ubuntu 22.10, the system froze again after calling the Gnome Display Manager, like it has been doing for 17 days now. Even this partial upgrade to Linux 5.19.0-15 did not solve anything.

Again separate the my bug report from the others, because my problem has nothing to do with the Virtualbox release nor with the Linux release.
It is only dependent on the Gnome desktop of 22.10!!!!

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

Can anyone give an educated guess how long it will take for the later/latest verison of VirtualBox to become available to Ubuntu's standard repo?

Hello, since I got some LaTeX failures on 6.1.38 (related to new LaTeX version, not vbox itself),
I did upload packages in my ppa, for people who don't want to wait for the SRU to have place.

https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/virtualbox-ppa/+packages

Fortunately LaTeX in Ubuntu 22.04 and 20.04 is able to correctly build the documentation.

This bug was fixed in the package virtualbox - 6.1.38-dfsg-2~build1

---------------
virtualbox (6.1.38-dfsg-2~build1) kinetic; urgency=medium

  * Upload to kinetic

virtualbox (6.1.38-dfsg-2) unstable; urgency=medium

  [ Andreas Beckmann ]
  * Switch to dh-sequence-dkms.
  * Declare Testsuite: autopkgtest-pkg-dkms.

  [ Gianfranco Costamagna ]
  * Drop utf8x from https://github.com/latex3/latex2e/issues/833
  * And replace double arrow with two different arrows (left and right)
    to avoid utf8 chars in documentation.

virtualbox (6.1.38-dfsg-1) unstable; urgency=medium

  * New upstream version 6.1.38-dfsg (Closes: #1012627, LP: #1988473)

 -- Gianfranco Costamagna <email address hidden> Tue, 06 Sep 2022 15:29:33 +0200

Ok, the LaTeX issues are somewhere sorted out, and upstream is looking also at eliminating utf8x characters from the manpage too.
I'll convert this bug into an SRU shortly.

I never used the Ubuntu versions of Virtualbox and I always downloaded Virtualbox directly from virtualbox.org. I never had these problems with 6.1.34 nor with 6.1.36 nor with 6.1.38 on none of my ~70 desktop VMs (all Windows releases from 1986 till 2022 and all Ubuntu LTS releases from 2004 till 2022). I only have a problem with the Ubuntu 22.10 VM.

I produced bug report #1988488 supposedly the same as #1988473 and my problem is NOT SOLVED yet!!

Ubuntu 22.10 has been running Virtualbox 6.1.36 and 6.1.38 and Linux 5.15.0-27 and 5.19.0-7. At all 4 possible configurations the system still freezes at the moment it calls the gnome display manager.

I uploaded virtualbox in unapproved queue for focal (20.04) and jammy (22.04).
Waiting for SRU team to have a look

Hello Chris, or anyone else affected,

Accepted virtualbox into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virtualbox/6.1.38-dfsg-3~ubuntu1.22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Chris, or anyone else affected,

Accepted virtualbox-ext-pack into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virtualbox-ext-pack/6.1.38-1~ubuntu1.22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Chris, or anyone else affected,

Accepted virtualbox-guest-additions-iso into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virtualbox-guest-additions-iso/6.1.38-1~ubuntu1.22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Chris, or anyone else affected,

Accepted virtualbox-hwe into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virtualbox-hwe/6.1.38-dfsg-3~ubuntu1.22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Chris, or anyone else affected,

Accepted virtualbox into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virtualbox/6.1.38-dfsg-3~ubuntu1.20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Chris, or anyone else affected,

Accepted virtualbox-guest-additions-iso into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virtualbox-guest-additions-iso/6.1.38-1~ubuntu1.20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Chris, or anyone else affected,

Accepted virtualbox-ext-pack into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virtualbox-ext-pack/6.1.38-1~ubuntu1.20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Chris, or anyone else affected,

Accepted virtualbox-hwe into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virtualbox-hwe/6.1.38-dfsg-3~ubuntu1.20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

I've enabled the proposed repository and I can see some of the new virtualbox packages as being upgradeable. But If I try to upgrade just virtualbox packages, I get an unmet dependency error. I don't want to upgrade all proposed packages for Jammy, so how should I proceed to test? I am booted into the version 47 kernel (had to do it via recovery mode).

Chris

@Chris, did you try apt install virtualbox?

and show some logs about the dependency errors? maybe they were just due to the outdated mirrors during build and publish

Hello,

I can confirm: upgrading to VirtualBox 6.1.38 seems to fix the problem in Ubuntu 22.04 (kernel 5.15.0-47). No crash so far in Win10 VM after upgrade.

Steps to install the VB 6.1.38:
- kernel upgraded to 5.15.0-47
- jammy-proposed enabled in dev. options
- packages installed using synaptic (or apt install?). These were upgraded from 6.1.34 to 6.1.38.
   virtualbox
   virtualbox-dkms
   virtualbox-qt

@Gianfranco, Łukasz: Thank you for your help!

gl

I too can confirm that 6.1.38 solves the problem. I had additional problems getting there because in my initial troubleshooting of VB, I wound up mangling 5.15.0-47. I also had tried to "upgrade" VB rather than install.

So:

reinstalled 5.15.0-47-generic
enabled jammy-proposed
installed VB, including extpack and dkms and additions

It all seems to work not. Win10 boots and handles networking. Thanks for making the package available.

Chris

The dist-upgrade itself of 22.10 did run without errors. Note that my
problem is not a crash, but the freezing of the screen just before
login. It occurs on a fresh install too, so we can forget about
dependency problem due to outdated mirrors also because I have the same
problem for more than 2 weeks and I reported it last week!

That freezing of Ubuntu 22.10 occurs with all combinations of Linux
5.15-27; 5.19.0-7; Virtualbox 6.1.36 and 6.1.38. Note that my
Virtualbox is from virtualbox.org and like I said I have absolutely no
problems with Ubuntu or any of the flavors of 22.04 and 20.04 with the
last 3 or 4 Virtualbox releases.

I can start tty3 while the Ubuntu screen is frozen and tty3 looks
completely normal, also when running "top" and looking at the
processes.

I tried Xubuntu 22.10 with Virtualbox 6.1.38 and it worked fine, but
the flavors are probably using xorg instead of wayland and only a
subset of the gnome software.

What logs from /var/log do you need?

On Thu, 2022-09-08 at 15:23 +0000, Gianfranco Costamagna wrote:
> and show some logs about the dependency errors? maybe they were just
> due
> to the outdated mirrors during build and publish
>

Since the kernel update to 5.15.0-47, all my virtualbox VMs had become barely usable. In all my Ubuntu guests, gnome-shell or compiz would crash quite often.

I installed the virtualbox update (6.1.38-dfsg-3~ubuntu1.22.04.1) from jammy-proposed, and I can confirm the problem is resolved. My VMs are now working normally, no more inopportune crashes in the guests.

Hello, thanks you all for the confirmation!
Also focal is good!

Hello,

I had got similar problems using Windows 10 guest on VirtualBox 6.1.34 on Ubuntu 22.04 host with kernel version 5.15.0-47.

I enabled pre-release updates and updated virtualbox, virtualbox-dkms, and virtualbox-qt packages from 6.1.34 to 6.1.38. I also installed the 6.1.38 Guest Additions inside the VM.

Everything looks like it is working like a charm.

Thank you very much!

(I don't know how to add/change tags.)

This bug was fixed in the package virtualbox - 6.1.38-dfsg-3~ubuntu1.22.04.1

---------------
virtualbox (6.1.38-dfsg-3~ubuntu1.22.04.1) jammy; urgency=medium

  * SRU the latest package for Ubuntu jammy (LP: #1988473)

 -- Gianfranco Costamagna <email address hidden> Wed, 07 Sep 2022 13:18:57 +0200

This bug was fixed in the package virtualbox-guest-additions-iso - 6.1.38-1~ubuntu1.22.04.1

---------------
virtualbox-guest-additions-iso (6.1.38-1~ubuntu1.22.04.1) jammy; urgency=medium

  * SRU the latest package for Ubuntu jammy (LP: #1988473)

 -- Gianfranco Costamagna <email address hidden> Wed, 07 Sep 2022 13:05:07 +0200

This bug was fixed in the package virtualbox-ext-pack - 6.1.38-1~ubuntu1.22.04.1

---------------
virtualbox-ext-pack (6.1.38-1~ubuntu1.22.04.1) jammy; urgency=medium

  * SRU the latest package for Ubuntu jammy (LP: #1988473)

 -- Gianfranco Costamagna <email address hidden> Wed, 07 Sep 2022 13:07:54 +0200

This bug was fixed in the package virtualbox-hwe - 6.1.38-dfsg-3~ubuntu1.22.04.1

---------------
virtualbox-hwe (6.1.38-dfsg-3~ubuntu1.22.04.1) jammy; urgency=medium

  * SRU the latest package for Ubuntu jammy (LP: #1988473)

 -- Gianfranco Costamagna <email address hidden> Wed, 07 Sep 2022 13:10:33 +0200

The verification of the Stable Release Update for virtualbox has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package virtualbox - 6.1.38-dfsg-3~ubuntu1.20.04.1

---------------
virtualbox (6.1.38-dfsg-3~ubuntu1.20.04.1) focal; urgency=medium

  * SRU the latest package for Ubuntu focal (LP: #1988473)
  * Revert drop of *guest-dkms packages for focal only.
    Such packages are still needed because kernel < 5.5. doesn't provide
    vboxsf
  * Revert switch to dh-sequence-dkms, not enough new dkms is available in
    focal

 -- Gianfranco Costamagna <email address hidden> Wed, 07 Sep 2022 13:18:57 +0200

This bug was fixed in the package virtualbox-guest-additions-iso - 6.1.38-1~ubuntu1.20.04.1

---------------
virtualbox-guest-additions-iso (6.1.38-1~ubuntu1.20.04.1) focal; urgency=medium

  * SRU the latest package for Ubuntu focal (LP: #1988473)

 -- Gianfranco Costamagna <email address hidden> Wed, 07 Sep 2022 13:05:07 +0200

This bug was fixed in the package virtualbox-ext-pack - 6.1.38-1~ubuntu1.20.04.1

---------------
virtualbox-ext-pack (6.1.38-1~ubuntu1.20.04.1) focal; urgency=medium

  * SRU the latest package for Ubuntu focal (LP: #1988473)
  * Revert compat level to 12, the last available in focal

 -- Gianfranco Costamagna <email address hidden> Wed, 07 Sep 2022 13:07:54 +0200

This bug was fixed in the package virtualbox-hwe - 6.1.38-dfsg-3~ubuntu1.20.04.1

---------------
virtualbox-hwe (6.1.38-dfsg-3~ubuntu1.20.04.1) focal; urgency=medium

  * SRU the latest package for Ubuntu focal (LP: #1988473)
  * Revert drop of *guest-dkms packages for focal only.
    Such packages are still needed because kernel < 5.5. doesn't provide
    vboxsf
  * Revert switch to dh-sequence-dkms, not enough new dkms is available in
    focal

 -- Gianfranco Costamagna <email address hidden> Wed, 07 Sep 2022 13:10:33 +0200