What is the correct way to install and enable VirtualBox Guest additions in Slackware 15?

decuser · 02-27-2023, 09:13 AM

I have seen some 14.2 videos and found slackbuilds and, etc. But what's the right way to get the guest additions installed in Slackware 15.

I mounted the dvd and ran bash VBoxLinuxAdditions.run and it complained about them already being there, but unless they're installed as part of the normal install, they shouldn't have been there. Also, after I rebooted, there were the same messages:

Code:

VirtualBox Guest Additions: VirtualBox Guest Additions kernel modules 6.1.40 r154048 are already available for kernel 5.15.19 and do require to be rebuilt.

VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted.

The thing is, now, the guest additions are working (I can resize the window in KDE and the resolution is updated automagically.

I don't mind it working, but I need some reassurance that it's supposed to work like this or what I need to do differently.

Thanks,
Will

ppr:kut · 02-27-2023, 02:50 PM

The linux kernel already includes the necessary kernel modules to get the guest additions working, and most functionality will work out of the box. For some things you might still need the guest additions installed, like shared clipboard, for example, or automatic rescaling if using the VMSVGA adapter.

The message comes from the guest additional installer that detects the modules from the linux kernel and wants to replace them with their out-of-tree versions shipped separately. Opinions on whether those are better differ, and Oracle is obviously biased. I'd say just try with the ones shipped with Slackware until you run into something that doesn't work for you.

decuser · 02-27-2023, 03:03 PM

Quote:

Originally Posted by ppr:kut

The linux kernel already includes the necessary kernel modules to get the guest additions working, and most functionality will work out of the box. For some things you might still need the guest additions installed, like shared clipboard, for example, or automatic rescaling if using the VMSVGA adapter.

So, if I want the rescaling to work, is my best approach to run the installer on the Oracle CD and just ignore the messages or to do it some other way?

ppr:kut · 02-28-2023, 01:24 AM

That is one option, yes. I never really use the installer so can't say if there's another way to /not/ get the messages. Maybe someone else can chime in about that.

Other options would be:
- The SlackBuild over on SBo
- My package for the virtualbox guest additions

decuser · 03-01-2023, 09:53 AM

Quote:

Originally Posted by ppr:kut

My package for the virtualbox guest additions

OK. Your package works and no errors or missing anything, etc. You're a wizard... I love that it works. But I would also like to get a clue as to how you created the package so I'm not reliant on your good graces in the future.

I have a vanilla, fully up-to-date, fully installed slackware 15 64 installed in Virtualbox. I don't mind manually installing a package or two out of necessity (like the guest extensions), but I would prefer to keep things as vanilla as possible. Your package is the first and only not-off-the-slackware-repo packages I have installed. So, how did you create it?

Will

ppr:kut · 03-01-2023, 10:35 AM

The sources for the package are here: https://repo.liwjatan.org/pprkut/15....ualbox-addons/

It's just a modified version of the SlackBuild on SBo though (also maintained by me)

decuser · 03-01-2023, 11:45 AM

As an SBO newbie, I dug around a bit and figured out what I think is the way this should work, tell me if I'm off target, please.

1. Get the SBO public key

Code:

wget https://slackbuilds.org/GPG-KEY
gpg --import GPG-KEY

2. Get the SBO package, sig, and source:

Code:

wget http://download.virtualbox.org/virtualbox/6.1.34/VirtualBox-6.1.34.tar.bz2
wget https://slackbuilds.org/slackbuilds/15.0/system/virtualbox-addons.tar.gz
wget https://slackbuilds.org/slackbuilds/15.0/system/virtualbox-addons.tar.gz.asc

3. Verify the package

Code:

gpg --verify virtualbox-addons.tar.gz.asc

4. Add a vboxadd user (the script warns and aborts if it doesn't exist)

Code:

useradd -u 215 -d /var/run/vboxadd -g 1 -s /bin/sh vboxadd

5. Unzip the package and copy over the source

Code:

tar xvf virtualbox-addons.tar.gz
mv VirtualBox-6.1.34.tar.bz2 virtualbox-addons/

6. Run the build script

Code:

cd virtualbox-addons
./virtualbox-addons.SlackBuild

It takes a few minutes to complete, have coffee.

7. Save off the package (you shared your version of this with me?)

Code:

scp /tmp/virtualbox-addons-6.1.34-x86_64-1_SBo.tgz wsenn@nebula:Desktop

8. Install the package

Code:

cd /tmp
installpkg virtualbox-addons-6.1.34-x86_64-1_SBo.tgz

9. Deal with any issues

Code:

Executing install script for virtualbox-addons-6.1.34-x86_64-1_SBo.tgz.
/bin/bash: line 35: usr/share/apps/kconf_update/kwin_blacklist.upd: No such file or directory
mv: cannot stat 'etc/rc.d/rc.vboxadd.new': No such file or directory
Package virtualbox-addons-6.1.34-x86_64-1_SBo.tgz installed.

These files don't exist, but it looks like it installed enough to work.

10. Reboot and test the scaling
It works with KDE!
Yay.

So, aside from the errors about the missing files, I didn't see anything wrong with the above and it worked. Is this reasonable? Also, it's 6.1.34 vs 6.1.40, I don't care, but VirtualBox tells me it's out of sync. As I mentioned, I'm an SBO newbie, is what you shared with me which is 6.1.40, your version that will eventually become the SBO version, or is it special?

Will

ppr:kut · 03-01-2023, 12:06 PM

The lines about the missing files is a bug in the SlackBuild, I'll have to look into that :-/

Otherwise, whatever works for you

There is no "one" way that is the "right" way. Some people prefer building from source using the SlackBuilds, some people prefer having packages ready (from trusted sources) they can install. Whatever you feel comfortable with is gonna be right for you.

The version in my repo is typically newer than what is on SBo, and both will indeed in irregular intervals be synced. There are subtle differences though, since SBo caters to a different target audience then my ready made packages (for example, my package will automatically create needed users/groups on install. With the package created from the SBo SlackBuild you have to do that yourself)

denydias · 03-01-2023, 02:58 PM

I understand this is about VirtualBox Guest Additions, but as it requires VirtualBox Extension Pack I'll leave a oneliner to automate the thing:

Code:

TMPDIR=/tmp VBoxManage extpack install $tmp/$extp --replace --accept-license=$UUID

Where:

TMPDIR overhides /dev/shm in case ramdisk run low on space, but it's optional;
$UUID is the license agreement UUID for batch install. It can be obtained by first running the command without --accept-license option, like bellow:

Code:

# TMPDIR=/tmp VBoxManage extpack install $tmp/$extp
VirtualBox Extension Pack Personal Use and Evaluation License (PUEL)
...
PLEASE READ THE FOLLOWING ORACLE VM VIRTUALBOX EXTENSION PACK PERSONAL
...
Do you agree to these license terms and conditions (y/n)? y

License accepted. For batch installaltion add
--accept-license=$UUID
to the VBoxManage command line.

rkelsen · 03-01-2023, 08:28 PM

Quote:

Originally Posted by decuser

As an SBO newbie, I dug around a bit and figured out what I think is the way this should work, tell me if I'm off target, please.

This is Slackware. You can use whatever methods work for you.

The way I do it: While the VM is running, I click on "Devices -> Insert Guest Additions CD Image."

Then, from within the VM, mount the CD and run the installation script.

I don't see any reason to create a package for it, and really, I can't be bothered.

ppr:kut · 03-02-2023, 01:12 AM

Quote:

Originally Posted by denydias

I understand this is about VirtualBox Guest Additions, but as it requires VirtualBox Extension Pack I'll leave a oneliner to automate the thing

The guest additions do not require the extension pack

yvesjv · 03-02-2023, 11:21 AM

Hey you guys just an FYI, we got stung at work with virtualbox.
Oracle demanded licensing paid when everyone thought it was free... it's not really.
Consequently I moved all my VMs to virtmanager qemu/kvm.

ctrlaltca · 03-02-2023, 11:38 AM

Virtualbox is GPL2, only the "VirtualBox Extension Pack" needs an enterprise license.
The extension pack adds support for RDP, disk encryption, NVMe and PXE boot; on old versions it was also needed for USB > 1.

yvesjv · 03-02-2023, 12:13 PM

That's where we all got stung... everyone installs it.

rkelsen · 03-02-2023, 04:35 PM

Quote:

Originally Posted by ctrlaltca

The extension pack adds support for RDP

That's dastardly!

Thanks for the heads up.