On 7/14/2021 9:00, S. wrote:
First of all, many thanks to Larry Finger for all
his hard work. It must be
frustrating for him, but I really appreciate all his work at maintaining
VirtualBox for openSUSE.
Second, I understand the issues with Oracle and
their development process and
attitude. If you can use something else besides VirtualBox as Larry suggests,
then do it. But the problem is that most users still love VirtualBox. As the
maintainer of the GeckoLinux spins, I can say from experience that the vast
majority of users expect VirtualBox support, so although I hate it myself I
basically have to deal with it and make sure it works. It would be nice if
issues like this were considered as blocking issues so that new kernels don't
appear in Tumbleweed until VirtualBox is known to work with them.
I do not support delaying the kernel for everyone just to accommodate Oracle's
way of (not) doing things. Users of specific software that frequently breaks
with new kernels should configure their system to keep an old kernel or two
The good news is that Oracle has created a patch that fixes the problem. It was
just over an hour from the time their fix was published until I was building and
testing a local version of VB.
The fix was pushed to OBS about 2 hours ago. It will take a few days for the fix
to propagate through OBS, but when it does, all of you will have full VB
capabilities on all kernels.
As for me, I can now get back to my regular life.