VirtualBox 6.1.34r150636 does not work on Debian Host (kernel 5.10.0-15-amd64)

[strik]

Hello,

I am using the VirtualBox debian packages (not the Debian provided ones) on a fully updated Debian Bullseye. VirtualBox guest tools are installed and current. Guest OS is Debian Bullseye, too.

Yesterday, I upgrade my kernel from linux-image-5.10.0-14 (which is based on 5.10.113) to linux-image-5.10.0-15 (which is based on 5.10.120).

Afterwards, I found that a Firefox instance started crashing - sometimes, directly on startup, sometimes, after some minutes browsing. However, it never lasted long before the crash. As I thought it might be a Firefox problem, I started several tests. I even went back to a snapshot that worked one month before: Firefox kept crashing and crashing.

I also found out that many other things did not work. Three times, the virtual Linux did not even boot, I ended in the emergency console. While doing an update of the base OS from an older snapshot, I noticed many hash errors. Unfortunately, I do not have any screen shots or logs of these.


After many, many tests, I found that the update of the Linux kernel on the Host caused the problem. If I boot the old one (linux-image-5.10.0-14, which is based on 5.10.113), then the crashes disappear immediately!


To be honest, I am not sure where to report this bug: Is it a Debian bug? Is it a kernel bug? Is it a VBox bug, which only shows on that kernel revision?

I added the VBox.log files for 5.10.0-14 (which does not crash) as well as for 5.10.0-15 (which crashes). Additionally, the output of the stress-ng program are included for both variants, too. That program was my simplest way to show a problem in the VM.

Does anyone have any idea what is going on, or where I should report this bug?

[fth0]

The actual problem is that VirtualBox 6.1.34 does not support Linux kernel 5.10.119+ on the host and will produce random crashes in the guest (pun intended ). See 20914 and Windows 10 Guest on Linux host dies seconds after boot for details.

[strik]

Indeed, I had already seen this other post, but as there was no 5.10.x mentioned (only 5.17.12 and up), I was not sure if it is somehow related.

I wanted to mention that other post, but forgot while posting.

So I will keep my old kernel until I see a new version that should fix this issue.

Thank you for your answer!

EDIT: I totally overlooked the second page of that link, where the exact same issue was mentioned. Bummer!

[fth0]

The VirtualBox test builds 6.1.35r151864 (and newer) are supposed to support Linux kernels 5.18, 5.17.12+, 5.15.44+, 5.10.119+ and more on the host and in the guest. Please report back if it solves the problem.