Ask Your Question

Kernel 5.0.8 breaks VB

asked 2019-04-24 15:01:05 -0500

mrhanky gravatar image

And yet AGAIN Fedora breaks VirtualBox after kernel upgrade.

What good is an operating system like Fedora when it breaks applications that they fully understand will happen because it always happens, and all those people who use VirtualBox have to try to find a fix?

It's absolutely ridiculous. It would make more sense if the experts at Fedora forbid VirtualBox installation as well as many other applications. At least users would understand that a different distro would be a better choice as opposed to having to try to find a fix or reload Fedora.

I really don't care what anyone has to say or Fedora for that matter. I'm sick of being told, "Oh, we don't maintain that."

edit retag flag offensive close merge delete


I install new kernels from testing right away, and it never breaks my VirtualBox. How and from what source did you install VB? Are your kernel modules properly building on reboot?

florian gravatar imageflorian ( 2019-04-24 21:16:23 -0500 )edit

If you don’t answer the question, you can’t expect to be helped. Re-asking the same question without providing additional information usually doesn’t help.

FYI, I’m running VB daily since many many years on the latest kernels that Fedora builds and I have not had any problems.

It must be related with the way you chose to install your software.

Happy to help!

florian gravatar imageflorian ( 2019-04-25 21:50:03 -0500 )edit

when VB kernel mods are compiled by akmods, "this" simply does not happen. So stop ranting and switch from the static compiled kmod package to akmod.

rdtcustomercare gravatar imagerdtcustomercare ( 2019-04-26 02:50:05 -0500 )edit

1 Answer

Sort by » oldest newest most voted

answered 2019-04-27 22:54:28 -0500

Benjamin Doron gravatar image

As I just posted: "I assume that your issue is module loading with kernel lockdown enabled (via secure boot or kernel command line, it makes no difference).

This issue is being tracked in red hat Bugzilla IDs 1696671 and 1701096 (5.0.8 fixed the first issue, exposing the second). You can read up on these bugs if you'd like, but they should be fixed in 5.0.10 which was just released by upstream. In a week, maybe 2, that kernel version should arrive in stable.

There was no need to insult anybody."

edit flag offensive delete link more

Question Tools

1 follower


Asked: 2019-04-24 15:01:05 -0500

Seen: 248 times

Last updated: Apr 27 '19