I'm on a Slackware64-current host running a Slackware64-current guest. This is what I get on installation.
Code: Select all
# /mnt/VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 6.1.38 Guest Additions for Linux........
VirtualBox Guest Additions installer
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules. This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Building the modules for kernel 5.19.6.
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted
./routines.sh: line 239: systemctl: command not found
VirtualBox Guest Additions kernel modules 6.1.38 r153438 are
already available for kernel 5.19.6 and do not require to be rebuilt.
Running kernel modules will not be replaced until the system is restarted
vboxadd-service.sh: Starting VirtualBox Guest Addition service.
I agree with @HarryMan, as you can see below, lsmod ran immediately after, the VirtualBox Guest Addition is indeed installed.
Code: Select all
# lsmod | grep vbox
vboxvideo 49152 0
drm_ttm_helper 16384 2 vmwgfx,vboxvideo
ttm 81920 3 vmwgfx,vboxvideo,drm_ttm_helper
drm_kms_helper 180224 2 vmwgfx,vboxvideo
drm 622592 6 vmwgfx,drm_kms_helper,vboxvideo,drm_ttm_helper,ttm
vboxguest 45056 1
This is what I get with a reboot.
Code: Select all
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: VirtualBox Guest Additions kernel modules 6.1.38
r153438 are
VirtualBox Guest Additions: already available for kernel 5.19.6 and do not
require to be rebuilt.
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted
vboxadd-service.sh: Starting VirtualBox Guest Addition service.
This is even more inconsistent. It tells the modules are already available and do not require a reboot, then it tells me that running modules will not be replaced until the system is restarted. (Ah, I was just restarted). Then it tell me it is starting the service. I has started, same result from lsmod above or am I expected to reboot continuously.
I will say this. It is an small improvement over 6.1.35 (and below) which produced this output at every boot. See my post
here.
Code: Select all
### Every boot.
VirtualBox Guest Additions: Starting.
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel
modules. This may take a while.
VirtualBox Guest Additions: To build modules for other installed kernels, run
VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup <version>
VirtualBox Guest Additions: or
VirtualBox Guest Additions: /sbin/rcvboxadd quicksetup all
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted
vboxadd-service.sh: Starting VirtualBox Guest Addition service.
There is also the issue of "./routines.sh: line 239: systemctl: command not found" which occurs in both the host and guest on installing. Slackware does not use systemd. The error appears to be harmless as VirtualBox is work just fine on both my host and guest but it shouldn't be there.