Kernel 5.0.8 breaks VB
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."
I install new kernels from
testingright away, and it never breaks my VirtualBox. How and from what source did you install VB? Are your kernel modules properly building on reboot?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!
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.