On Fri, Feb 07, 2020 at 10:14:16AM +0100, Dan Čermák wrote:
Jiri Slaby <jslaby(a)suse.cz> writes:
The virtualbox woes with 5.5 will keep that move
more painful than ever.
You have to complain to virtualbox authors. It's apparently their fault
not to upstream the modules in the past decade. It cannot stop new
kernels to roll in openSUSE.
The other option is to politely ask our vbox maintainer to keep vbox up
with 5.5. What's the problem, actually?
As the maintainer of Vagrant, that was designed to primarily use
VirtualBox (not on openSUSE though), I'd like to know too.
The "issues with virtualbox vs. new kernel" usually mean there is some
change in the internal kernel API which the out-of-tree modules need to
be adjusted to. It's the same with any other project dependent on
out-of-tree modules (VMware, NVidia, ...).
But I have no idea what exactly does virtualbox have problem with as 5.5
was in fact one of the few recent versions which did _not_ break the
build of host modules for VMware Workstation/Player.
In any case, I agree that it's a problem of virtualbox and no reason to
delay the switch to 5.5 kernel (unless there actually is a kernel bug).
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org