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.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Rep:
Quote:
Originally Posted by chrisretusn
Optional. I don't install the Guest Additions on Slackware, unless I am playing with them. I don't like the way it installs anyway. I do my sharing via NFS shares. I am fine with 800x600 resolution. All most everything I do in a Slackware VM is via the CLI anyway.
This is because of "xf86-video-vboxvideo" package that is part of Slackware. If you want to install the Guest Additions you need to remove this package.
No xf86-video-vboxvideo has no effect on VirtualBox Guest Additions installation.
You can have both without any issues.
Now I don't know if you run Slackware current, but the slackbuild script of virtualbox at current github at ponce, includes the guest additions. And it's not like it's a huge amount of extras diskspace.
Optional. I don't install the Guest Additions on Slackware, unless I am playing with them. I don't like the way it installs anyway. I do my sharing via NFS shares. I am fine with 800x600 resolution. All most everything I do in a Slackware VM is via the CLI anyway.
This is because of "xf86-video-vboxvideo" package that is part of Slackware. If you want to install the Guest Additions you need to remove this package.
Quote:
Originally Posted by Aeterna
No xf86-video-vboxvideo has no effect on VirtualBox Guest Additions installation.
You can have both without any issues.
I was responding this this statement:
Quote:
Originally Posted by linuxxer
When I tried to install Guest Addition on Slackware VMs, it display prompt it is already install.
My answer is correct, except perhaps that last sentence, since the installer lets you proceed. The reason for this display prompt is the package "xf86-video-vboxvideo".
Code:
Verifying archive integrity... All good.
Uncompressing VirtualBox 6.1.19 Guest Additions for Linux........
VirtualBox Guest Additions installer
./install.sh: line 143: VBoxControl: command not found
This system appears to have a version of the VirtualBox Guest Additions
already installed. If it is part of the operating system and kept up-to-date,
there is most likely no need to replace it. If it is not up-to-date, you
should get a notification when you start the system. If you wish to replace
it with this version, please do not continue with this installation now, but
instead remove the current version first, following the instructions for the
operating system.
If your system simply has the remains of a version of the Additions you could
not remove you should probably continue now, and these will be removed during
installation.
Do you wish to continue? [yes or no]
Yes you can continue and it will install.
Code:
touch: cannot touch '/var/lib/VBoxGuestAdditions/skip-5.10.18': No such file or directory
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.10.18.
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted
Building the VirtualBox Guest Additions kernel modules. This may take a while.
To build modules for other installed kernels, run
/sbin/rcvboxadd quicksetup <version>
or
/sbin/rcvboxadd quicksetup all
Running kernel modules will not be replaced until the system is restarted
vboxadd-service.sh: Starting VirtualBox Guest Addition service.
If you remove the "xf86-video-vboxvideo" package you will not get that prompt.
You want to leave it in fine. I prefer to remove it. Your choice.
Last edited by chrisretusn; 02-27-2021 at 03:19 AM.
Just now I started using VirtualBox 6.1.18 on my Slackware Alpha 1 system for testing and programming purpose.
I don't install VirtualBox Guest Addition on other Linux distro.
Installation of VirtualBox guest addition is necessary for Slackware VM? Or is it optional?
Because I don't need extra functionality like, share clipboard between host and guest system and share folder using VirtualBox "Shared Folders" functionality.
When I tried to install Guest Addition on Slackware VMs, it display prompt it is already install.
Please suggest.
Thanks in advance.
My system is -
Slackware 14.2 on the host running virtualBox 5.0.40
Slackware Current on the guest with Kernel 5.10.16
The Guests Kernel 5.10.16 resizes my screen and supplies shared folders without issue.
The only thing missing is bi-directional copy/paste, but with shared folders there are work arounds.
My experience over the last month or so is that if I install GuestAdditions on a guest it breaks it big-time. So I'm prepared to live without bi-directional copy/paste if it means I have a workable guest that resizes the display and has shared folders.
I have been using VirtualBox for years. I am running it in a slackware64-current host with kernel 5.11.1, via the KDE Plasma Desktop.
My guest machines are:
Slackware/
Slackware64/
Slackware-14.2/
Slackware64-14.2/
The first four are clean installs of Slackware that I use for testing, building. Snapshots help keep them clean.
Slackware-test/
Slackware64-14.2Clone/
Slackware64-elilo/
Slackware64-live/
Slackware64-racer/
Windows10/
eComStation/
I only use Guest Additions in the Windows10 guest. I have tried Guess Additions in Slackware, have it installed in one right now.
This is the most annoying part abput guest additions, at every boot:
Code:
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.
Except for Windows10 I share between the host, guest and between other guest via NFS.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Rep:
Quote:
Originally Posted by chrisretusn
I was responding this this statement:
My answer is correct, except perhaps that last sentence, since the installer lets you proceed. The reason for this display prompt is the package "xf86-video-vboxvideo".
Code:
Verifying archive integrity... All good.
Uncompressing VirtualBox 6.1.19 Guest Additions for Linux........
VirtualBox Guest Additions installer
./install.sh: line 143: VBoxControl: command not found
This system appears to have a version of the VirtualBox Guest Additions
already installed. If it is part of the operating system and kept up-to-date,
there is most likely no need to replace it. If it is not up-to-date, you
should get a notification when you start the system. If you wish to replace
it with this version, please do not continue with this installation now, but
instead remove the current version first, following the instructions for the
operating system.
If your system simply has the remains of a version of the Additions you could
not remove you should probably continue now, and these will be removed during
installation.
Do you wish to continue? [yes or no]
Yes you can continue and it will install.
Code:
touch: cannot touch '/var/lib/VBoxGuestAdditions/skip-5.10.18': No such file or directory
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.10.18.
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted
Building the VirtualBox Guest Additions kernel modules. This may take a while.
To build modules for other installed kernels, run
/sbin/rcvboxadd quicksetup <version>
or
/sbin/rcvboxadd quicksetup all
Running kernel modules will not be replaced until the system is restarted
vboxadd-service.sh: Starting VirtualBox Guest Addition service.
If you remove the "xf86-video-vboxvideo" package you will not get that prompt.
You want to leave it in fine. I prefer to remove it. Your choice.
No, I don't this prompt in Slackware client with installed xf86-video-vboxvideo-1.0.0-x86_64-5
I don't see it when upgrading virtualbox guest additions,
I don't see it when installing virtualbox guest additions on the system when virtualbox guest additions were removed first before installation of the new version (in this instsnce I remove virtualbox guest additions old version, reboot snd install new version)
I don't see it when virtualbox guest additions are installed for the new kernel
I use original Oracle package though, not Slackware script. This may a difference.
I noticed this prompt on some client linux distros (e.g. debian or Arch derivatives), but not on Slackware or Gentoo
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Rep:
to prove my point I just uninstalled VirtualBox Guest Additions. powered down Slackware VM client and run script installation again:
Quote:
sudo sh VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 6.1.18 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.4.101-cephei.
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted
Building the VirtualBox Guest Additions kernel modules. This may take a while.
To build modules for other installed kernels, run
/sbin/rcvboxadd quicksetup <version>
or
/sbin/rcvboxadd quicksetup all
Running kernel modules will not be replaced until the system is restarted
vboxadd-service.sh: Starting VirtualBox Guest Addition service.
and
Quote:
slackpkg search xf86-video-vboxvideo
Looking for xf86-video-vboxvideo in package list. Please wait... DONE
The list below shows all packages with name matching "xf86-video-vboxvideo".
You can search specific files using "slackpkg file-search file".
based on your output from installation script, I think that you are using Slackware VB package.
I use Oracle instaler
Quote:
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.
this is just script checking if modules are installed for current kernel. If so, script does nothing and if modules are missing then vb script builds modules for a new kernel.
I see modules building only if I install a ne kernel.
to prove my point I just uninstalled VirtualBox Guest Additions. powered down Slackware VM client and run script installation again:
Proving my point.
VirtualBox Version 6.1.19 r142917 with Extension Pack-6.1.19-142894 installed.
Clean up to date slackware64-current install, ChangeLog.txt: Sat Feb 27 19:26:22 UTC 2021
Snapshot taken before Start of the virtual machine.
Logged in as root at the CLI (runlevel 3)
Devices > Insert Guest Additions CD Image.
Code:
mount /dev/sr0 /mnt
mount: /mnt: WARNING: source write-protected, mounted read-only.
/mnt/VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 6.1.19 Guest Additions for Linux........
VirtualBox Guest Additions installer
./install.sh: line 143: VBoxControl: command not found
This system appears to have a version of the VirtualBox Guest Additions
already installed. If it is part of the operating system and kept up-to-date,
there is most likely no need to replace it. If it is not up-to-date, you
should get a notification when you start the system. If you wish to replace
it with this version, please do not continue with this installation now, but
instead remove the current version first, following the instructions for the
operating system.
If your system simply has the remains of a version of the Additions you could
not remove you should probably continue now, and these will be removed during
installation.
Do you wish to continue? [yes or no]
Cancelling installation.
removepkg xf86-video-vboxvideo
Removing package: xf86-video-vboxvideo-1.0.0-x86_64-5
Removing files:
--> Deleting /usr/doc/xf86-video-vboxvideo-1.0.0/COPYING
--> Deleting /usr/doc/xf86-video-vboxvideo-1.0.0/ChangeLog
--> Deleting /usr/doc/xf86-video-vboxvideo-1.0.0/INSTALL
--> Deleting /usr/doc/xf86-video-vboxvideo-1.0.0/README
--> Deleting /usr/lib64/xorg/modules/drivers/vboxvideo_drv.la
--> Deleting /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so
--> Deleting /usr/man/man4/vboxvideo.4.gz
--> Deleting empty directory /usr/doc/xf86-video-vboxvideo-1.0.0/
/mnt/VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 6.1.19 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.10.19.
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted
Building the VirtualBox Guest Additions kernel modules. This may take a while.
To build modules for other installed kernels, run
/sbin/rcvboxadd quicksetup <version>
or
/sbin/rcvboxadd quicksetup all
Running kernel modules will not be replaced until the system is restarted
vboxadd-service.sh: Starting VirtualBox Guest Addition service.
Quote:
based on your output from installation script, I think that you are using Slackware VB package.
cat vbox-install.log
VirtualBox 6.1.19 r142917 installer, built 2021-02-23T17:34:47Z.
Testing system setup...
Removing previous installation of VirtualBox 6.1.19 r142917 from /opt/VirtualBox
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
cat vbox-setup.log
Building the main VirtualBox module.
Building the net filter module.
Building the net adaptor module
Yes the installer will let you install. I was wrong in part with my earlier statement to this:
Quote:
Originally Posted by linuxxer
When I tried to install Guest Addition on Slackware VMs, it display prompt it is already install.
My reply to that was:
Quote:
Originally Posted by chrisretusn
This is because of "xf86-video-vboxvideo" package that is part of Slackware.If you want to install the Guest Additions you need to remove this package.
The part I was wrong with was the last sentence (red). You do not "need to remove" "to install". I was absolutely correct in my first sentence (lime).
What happens to those drivers from the xf86-video-vboxvideo package?
There are deleted.
Restore snapshot, boot to clean install.
Code:
ls -l /usr/lib64/xorg/modules/drivers/vboxvideo_drv*
-rwxr-xr-x 1 root root 966 Feb 13 21:18 /usr/lib64/xorg/modules/drivers/vboxvideo_drv.la*
-rwxr-xr-x 1 root root 39864 Feb 13 21:18 /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so*
mount /dev/sr0 /mnt
mount: /mnt: WARNING: source write-protected, mounted read-only.
/mnt/VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 6.1.19 Guest Additions for Linux........
VirtualBox Guest Additions installer
./install.sh: line 143: VBoxControl: command not found
This system appears to have a version of the VirtualBox Guest Additions
already installed. If it is part of the operating system and kept up-to-date,
there is most likely no need to replace it. If it is not up-to-date, you
should get a notification when you start the system. If you wish to replace
it with this version, please do not continue with this installation now, but
instead remove the current version first, following the instructions for the
operating system.
If your system simply has the remains of a version of the Additions you could
not remove you should probably continue now, and these will be removed during
installation.
Do you wish to continue? [yes or no]
touch: cannot touch '/var/lib/VBoxGuestAdditions/skip-5.10.19': No such file or directory
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.10.19.
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted
Building the VirtualBox Guest Additions kernel modules. This may take a while.
To build modules for other installed kernels, run
/sbin/rcvboxadd quicksetup <version>
or
/sbin/rcvboxadd quicksetup all
Running kernel modules will not be replaced until the system is restarted
vboxadd-service.sh: Starting VirtualBox Guest Addition service.
ls -l /usr/lib64/xorg/modules/drivers/vboxvideo_drv*
/bin/ls: cannot access '/usr/lib64/xorg/modules/drivers/vboxvideo_drv.*': No such file or directory
/opt/VBoxGuestAdditions-6.1.19/uninstall.sh
Removing installed version 6.1.19 of VirtualBox Guest Additions...
vboxadd-service.sh: Stopping VirtualBox Guest Addition service.
You may need to restart your guest system to finish removing guest drivers.
ls -l /usr/lib64/xorg/modules/drivers/vboxvideo_drv*
/bin/ls: cannot access '/usr/lib64/xorg/modules/drivers/vboxvideo_drv.*': No such file or directory
Restart the VM.
After logged in as root
Code:
ls -l /usr/lib64/xorg/modules/drivers/vboxvideo_drv*
/bin/ls: cannot access '/usr/lib64/xorg/modules/drivers/vboxvideo_drv.*': No such file or directory
Those drivers are gone, if you want them back you have to install xf86-video-vboxvideo again.
If you kept it: "slackpkg reinstall xf86-video-vboxvideo"
Last edited by chrisretusn; 02-28-2021 at 04:53 AM.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,011
Rep:
Quote:
Originally Posted by chrisretusn
Proving my point.
VirtualBox Version 6.1.19 r142917 with Extension Pack-6.1.19-142894 installed.
Clean up to date slackware64-current install, ChangeLog.txt: Sat Feb 27 19:26:22 UTC 2021
Snapshot taken before Start of the virtual machine.
Logged in as root at the CLI (runlevel 3)
Devices > Insert Guest Additions CD Image.
Code:
mount /dev/sr0 /mnt
mount: /mnt: WARNING: source write-protected, mounted read-only.
/mnt/VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 6.1.19 Guest Additions for Linux........
VirtualBox Guest Additions installer
./install.sh: line 143: VBoxControl: command not found
This system appears to have a version of the VirtualBox Guest Additions
already installed. If it is part of the operating system and kept up-to-date,
there is most likely no need to replace it. If it is not up-to-date, you
should get a notification when you start the system. If you wish to replace
it with this version, please do not continue with this installation now, but
instead remove the current version first, following the instructions for the
operating system.
If your system simply has the remains of a version of the Additions you could
not remove you should probably continue now, and these will be removed during
installation.
Do you wish to continue? [yes or no]
Cancelling installation.
removepkg xf86-video-vboxvideo
Removing package: xf86-video-vboxvideo-1.0.0-x86_64-5
Removing files:
--> Deleting /usr/doc/xf86-video-vboxvideo-1.0.0/COPYING
--> Deleting /usr/doc/xf86-video-vboxvideo-1.0.0/ChangeLog
--> Deleting /usr/doc/xf86-video-vboxvideo-1.0.0/INSTALL
--> Deleting /usr/doc/xf86-video-vboxvideo-1.0.0/README
--> Deleting /usr/lib64/xorg/modules/drivers/vboxvideo_drv.la
--> Deleting /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so
--> Deleting /usr/man/man4/vboxvideo.4.gz
--> Deleting empty directory /usr/doc/xf86-video-vboxvideo-1.0.0/
/mnt/VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 6.1.19 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.10.19.
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted
Building the VirtualBox Guest Additions kernel modules. This may take a while.
To build modules for other installed kernels, run
/sbin/rcvboxadd quicksetup <version>
or
/sbin/rcvboxadd quicksetup all
Running kernel modules will not be replaced until the system is restarted
vboxadd-service.sh: Starting VirtualBox Guest Addition service.
cat vbox-install.log
VirtualBox 6.1.19 r142917 installer, built 2021-02-23T17:34:47Z.
Testing system setup...
Removing previous installation of VirtualBox 6.1.19 r142917 from /opt/VirtualBox
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
cat vbox-setup.log
Building the main VirtualBox module.
Building the net filter module.
Building the net adaptor module
Yes the installer will let you install. I was wrong in part with my earlier statement to this:
My reply to that was:
The part I was wrong with was the last sentence (red). You do not "need to remove" "to install". I was absolutely correct in my first sentence (lime).
What happens to those drivers from the xf86-video-vboxvideo package?
There are deleted.
Restore snapshot, boot to clean install.
Code:
ls -l /usr/lib64/xorg/modules/drivers/vboxvideo_drv*
-rwxr-xr-x 1 root root 966 Feb 13 21:18 /usr/lib64/xorg/modules/drivers/vboxvideo_drv.la*
-rwxr-xr-x 1 root root 39864 Feb 13 21:18 /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so*
mount /dev/sr0 /mnt
mount: /mnt: WARNING: source write-protected, mounted read-only.
/mnt/VBoxLinuxAdditions.run
Verifying archive integrity... All good.
Uncompressing VirtualBox 6.1.19 Guest Additions for Linux........
VirtualBox Guest Additions installer
./install.sh: line 143: VBoxControl: command not found
This system appears to have a version of the VirtualBox Guest Additions
already installed. If it is part of the operating system and kept up-to-date,
there is most likely no need to replace it. If it is not up-to-date, you
should get a notification when you start the system. If you wish to replace
it with this version, please do not continue with this installation now, but
instead remove the current version first, following the instructions for the
operating system.
If your system simply has the remains of a version of the Additions you could
not remove you should probably continue now, and these will be removed during
installation.
Do you wish to continue? [yes or no]
touch: cannot touch '/var/lib/VBoxGuestAdditions/skip-5.10.19': No such file or directory
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.10.19.
VirtualBox Guest Additions: Running kernel modules will not be replaced until
the system is restarted
Building the VirtualBox Guest Additions kernel modules. This may take a while.
To build modules for other installed kernels, run
/sbin/rcvboxadd quicksetup <version>
or
/sbin/rcvboxadd quicksetup all
Running kernel modules will not be replaced until the system is restarted
vboxadd-service.sh: Starting VirtualBox Guest Addition service.
ls -l /usr/lib64/xorg/modules/drivers/vboxvideo_drv*
/bin/ls: cannot access '/usr/lib64/xorg/modules/drivers/vboxvideo_drv.*': No such file or directory
/opt/VBoxGuestAdditions-6.1.19/uninstall.sh
Removing installed version 6.1.19 of VirtualBox Guest Additions...
vboxadd-service.sh: Stopping VirtualBox Guest Addition service.
You may need to restart your guest system to finish removing guest drivers.
ls -l /usr/lib64/xorg/modules/drivers/vboxvideo_drv*
/bin/ls: cannot access '/usr/lib64/xorg/modules/drivers/vboxvideo_drv.*': No such file or directory
Restart the VM.
After logged in as root
Code:
ls -l /usr/lib64/xorg/modules/drivers/vboxvideo_drv*
/bin/ls: cannot access '/usr/lib64/xorg/modules/drivers/vboxvideo_drv.*': No such file or directory
Those drivers are gone, if you want them back you have to install xf86-video-vboxvideo again.
If you kept it: "slackpkg reinstall xf86-video-vboxvideo"
well then I was wrong also:
prompt appears first time but not after that (unless you reinstall it) because vboxvideo_drv is removed.
Good to know
Everything appears to be working. Except for this problem
On the host I use a directory to hold scripts, /usr/local/aikbin, which I share across all my guest machines. When I attempt to run any of the scripts from this shared folder I get unexpected results.
290 darkstar.example.net: /root $ /usr/local/bin/build_packages.ksh
must either ponce or slackbuild
On line 282 I get the unexpected result - calling the script from a shared folder. The script is in the PATH.
On line 284 when I precede the script with ksh I get the expected result - calling the script is in the shared folder. The shared folder is in the PATH.
On line 287 I copy the script to a non-shared folder.
On line 289 I call the script from the shared folder stating the path explicitly - same unexpected result
On line 290 I call the script from the non-shared folder stating the path explicitly - get the expected result
Is there anything I can do to get the expected results in all cases? Is this one for Oracle?
Everything appears to be working. Except for this problem
On the host I use a directory to hold scripts, /usr/local/aikbin, which I share across all my guest machines. When I attempt to run any of the scripts from this shared folder I get unexpected results.
I've managed to overcome this problem by switching Graphics Controllers.
Originally I'd selected the VMSVGA Graphics Controller because each time I selected another, such as VBOXVGA, in Settings -> Display I got this message -
Quote:
The virtual machine is configured to use a graphics controller other than the recommended one (VMSVGA). Please consider switching unless you have a good reason to keep the currently selected graphics controller.
Anyway I decided I had good reason and selected VBOXVGA. Started the machine and got a Seg fault.
Changed back to VMSVGA. Started machine successfully. Uninstalled Guest Additions. Stopped the machine.
Changed back to VBOXVGA. Started machine successfully.
Got shared folders and Auto-resize Guest Display.
As an added bonus I no longer get the annoying unexpected results
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
