VirtualBox and Linux kernel 5.16.0

Discussions related to using VirtualBox on Linux hosts.
Post Reply
nixuser
Posts: 32
Joined: 12. Dec 2018, 04:56

VirtualBox and Linux kernel 5.16.0

Post by nixuser »

I'm guessing as usual the new Linux kernel 5.16.0 will break VirtualBox Linux hosts when it drops. As it is already at rc7 it isn't far off. I expect Fedora and openSUSE Tumbleweed will get it shortly thereafter (possibly late January or early February?). Just wondering if anyone has experimented with it and how major the issues are going to be.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: VirtualBox and Linux kernel 5.16.0

Post by scottgus1 »

I have no experience with any Linux kernels. But having read the forum, I have seen that the devs often need a couple months-ish to get Virtualbox caught up to new kernels. So only update test hosts. Wait to update hosts you need to have stable Virtualbox running on, until the test hosts work well, and take good backups.
towo2099
Volunteer
Posts: 362
Joined: 18. Aug 2014, 21:53
Primary OS: Debian Sid
VBox Version: PUEL
Guest OSses: Android, Linux

Re: VirtualBox and Linux kernel 5.16.0

Post by towo2099 »

Code: Select all

towo:Defiant> dpkg -l | grep virtualbox
ii  virtualbox-6.1                                6.1.30-148432~Debian~bullseye        amd64        Oracle VM VirtualBox
It's playing nice with kernel 5.16-rc7.

Code: Select all

~
towo:Defiant> inxi -S
System:
  Host: Defiant Kernel: 5.16.0-rc7-siduction-amd64 x86_64 bits: 64
    Desktop: KDE Plasma 5.23.4
    Distro: siduction 18.3.0 Patience - kde - (202010061355)
nixuser
Posts: 32
Joined: 12. Dec 2018, 04:56

Re: VirtualBox and Linux kernel 5.16.0

Post by nixuser »

Thanks. The release notes for VirtualBox 6.1.30 did indicate initial support for kernel 5.16 was included, but it was early in the release cycle and a lot can happen between then and the release point, which I feel is close.

@scottgus1 Yes my usual tactic is to block the kernel from updating to a new stream until I know VirtualBox is going to run properly.
Post Reply