SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Virtualbox 6.0.14 kernel modules did not compile against the latest 5.4.x kernel in slackware-current. The attached patch worked for me.
There are multiple copies of cdefs.h and the-linux-kernel.h, os if your copies aren't hard linked, you may have to copy the patched file over the other copies.
Kudos to you @rahrah! For pointing out the upstream discussion, for the patch which have worked great and for bringing my dev env back on duty.
Others have pointed that VirtualBox 6.0.15 testbuild also worked with kernel 5.4.1. But to install a testbuild one need to uninstall the stable one then install the testbuild. Once the stable build is released from the testbuild, then the testbuild should also be uninstalled so the stable can be installed again. Too much hassle...
The patch you suggest does the job for VirtualBox 6.0.14 with no testbuild involved, which is a much more elegant solution IMHO.
For future reference, to apply the patch, copy de contents of the OP, save to "/opt/VirtualBox/src/vboxhost/kernel541.patch" then run:
Code:
# cd /opt/VirtualBox/src/vboxhost
# patch -p1 <kernel541.patch
# vboxconfig
Then you're done. Just open VirtualBox and run your VMs as usual.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Rep:
@denydias
Quote:
Others have pointed that VirtualBox 6.0.15 testbuild also worked with kernel 5.4.1. But to install a testbuild one need to uninstall the stable one then install the testbuild. Once the stable build is released from the testbuild, then the testbuild should also be uninstalled so the stable can be installed again. Too much hassle...
Nope,
just install 6.0.15 over 6.0.14. No need to uninstall first old (stable) and install next a new version (testbuild) and then when it come repead uninstall/install with new stable version.
Nope,
just install 6.0.15 over 6.0.14. No need to uninstall first old (stable) and install next a new version (testbuild) and then when it come repead uninstall/install with new stable version.
That's not what testbuild documentation says. Quoting:
Installing Linux test builds
Test builds for Linux hosts are generally packed up in a shell script installer with the extension ".run". To install them, you first need to remove your existing VirtualBox installation (but not your virtual machines - they will continue to work with the test build) and then execute the installer. To remove the test build again, execute the installer with the parameter "uninstall" on the command line.
Edit: btw, I tried to install 6.0.15 testcase on top of 6.0.14 stable without uninstalling it first. It doesn't worked for me tough.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Rep:
Quote:
Originally Posted by denydias
That's not what testbuild documentation says. Quoting:
Installing Linux test builds
Test builds for Linux hosts are generally packed up in a shell script installer with the extension ".run". To install them, you first need to remove your existing VirtualBox installation (but not your virtual machines - they will continue to work with the test build) and then execute the installer. To remove the test build again, execute the installer with the parameter "uninstall" on the command line.
Edit: btw, I tried to install 6.0.15 testcase on top of 6.0.14 stable without uninstalling it first. It doesn't worked for me tough.
You are correct. Sorry. However, I only followed uninstall/install/uninstall/install routine only for RC but I never had any issues with client VM when just updating installation to test or upgrading test to official installation
I followed the uninstall/install route. It eventually worked for me.
On two guests the uninstall took about 20 minutes to run. When finished it appeared to have removed a lot more than what I was expecting. I got ktown installed on these failing VirtualBox hosts. I'd lost the following -
in init 4 the ability to type in a password on the plasma login dialog
in init 4 the ability to move the mouse on the plasma login dialog
in init 3 eth0 was missing
in init 3 couldn't mount a previously downloaded VBoxGuestAdditions.iso got error "can't open blockdev"
in init 3 couldn't start udev because of missing modules
A sorry mess.
At this stage I thought I should try to reinstall the kernel packages by running
Code:
slackpkg reinstall kernel*
the packages to install were still in the cache. This was successful.
Rebooted and all the above problems went away, though when I booted to init 4 just got a black screen.
Booted to init 3 which now allowed me to
mount the testcase VBoxGuestAdditions.iso for 6.0.15
run VBoxLinuxAdditions.run
Rebooted to init 4 everything now in working order.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Rep:
Quote:
Originally Posted by aikempshall
I followed the uninstall/install route. It eventually worked for me.
On two guests the uninstall took about 20 minutes to run. When finished it appeared to have removed a lot more than what I was expecting. I got ktown installed on these failing VirtualBox hosts. I'd lost the following -
in init 4 the ability to type in a password on the plasma login dialog
in init 4 the ability to move the mouse on the plasma login dialog
in init 3 eth0 was missing
in init 3 couldn't mount a previously downloaded VBoxGuestAdditions.iso got error "can't open blockdev"
in init 3 couldn't start udev because of missing modules
A sorry mess.
At this stage I thought I should try to reinstall the kernel packages by running
Code:
slackpkg reinstall kernel*
the packages to install were still in the cache. This was successful.
Rebooted and all the above problems went away, though when I booted to init 4 just got a black screen.
Booted to init 3 which now allowed me to
mount the testcase VBoxGuestAdditions.iso for 6.0.15
run VBoxLinuxAdditions.run
Rebooted to init 4 everything now in working order.
Interesting. This is what I did.
attached VBoxGuestAdditions_6.0.15-134636.iso through VM host to all VM clients (3xlinux, and Windows 8.1, BSDs either do not support VB or require different setup for the upgrade)
start VM client
mount iso
from iso run
sudo sh VBoxLinuxAdditions.run
Installer automatically removed previous version of VBoxGuestAdditions and installed new (6.0.15) version.
reboot
That is all, took 5 min without any issues.
I run VM on a 5yrs old laptop and VM host is Slackware-current, though I doubt that distro matters.
I don't know why @aikempshall have so much trouble or why @denydias could not update VM host without uninstalling previous version first (this actually seems fishy).
Unless you are running VM installation from sbo, I don't see why you would have so much problems.
I don't know why @aikempshall have so much trouble or why @denydias could not update VM host without uninstalling previous version first (this actually seems fishy).
What looks fishy to me is someone finding fishy other people statements about their very own experience.
Maybe, and just maybe, VirtualBox 6.0.15 is a testbuild at this moment because the varying results it produces. Also maybe, and just maybe, the definition of testbuild is something that works for you in a different way that works for others.
Interesting. This is what I did.
attached VBoxGuestAdditions_6.0.15-134636.iso through VM host to all VM clients (3xlinux, and Windows 8.1, BSDs either do not support VB or require different setup for the upgrade)
start VM client
mount iso
from iso run
sudo sh VBoxLinuxAdditions.run
Installer automatically removed previous version of VBoxGuestAdditions and installed new (6.0.15) version.
reboot
That is all, took 5 min without any issues.
I run VM on a 5yrs old laptop and VM host is Slackware-current, though I doubt that distro matters.
I don't know why @aikempshall have so much trouble or why @denydias could not update VM host without uninstalling previous version first (this actually seems fishy).
Unless you are running VM installation from sbo, I don't see why you would have so much problems.
For me it could have been because of one or more of these -
which kernel is in use generic, huge or some other. On one of my guests I had huge and on the others I had generic.
which VBoxGuestAdditions was being upgraded. Not gone back to look, but I seem to remember I might have had 6.0.1 on some guests and 6.0.14 on others
Agreed should be a short task and complete without issue. In Slackware we seem to be ahead of the crowd here - no complaints.
The post I'm sure will help people. I'd never heard of testcase VBoxGuestAdditions builds before. Certainly helped me.
Don't know how many minutes it took me on the final guest, it wasn't long.
Kudos to you @rahrah! For pointing out the upstream discussion, for the patch which have worked great and for bringing my dev env back on duty.
Others have pointed that VirtualBox 6.0.15 testbuild also worked with kernel 5.4.1. But to install a testbuild one need to uninstall the stable one then install the testbuild. Once the stable build is released from the testbuild, then the testbuild should also be uninstalled so the stable can be installed again. Too much hassle...
The patch you suggest does the job for VirtualBox 6.0.14 with no testbuild involved, which is a much more elegant solution IMHO.
For future reference, to apply the patch, copy de contents of the OP, save to "/opt/VirtualBox/src/vboxhost/kernel541.patch" then run:
Code:
# cd /opt/VirtualBox/src/vboxhost
# patch -p1 <kernel541.patch
# vboxconfig
Then you're done. Just open VirtualBox and run your VMs as usual.
Thank you both, rahrah and denydias: with your patch and instructions, now VirtualBox 6.0.14 play very very well for me.
Just thought I'd throw this in. I running VirtualBox Version 6.1.0 r135406 with kernel 5.4.3 no issues. This is on a Slackware64-current host and using a clean Slackware64-current guest. I previously had testing 6.0.15-135299 installed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.