Virtualbox: Failed to set up vboxadd

Johncc330 · 03-01-2018, 10:29 AM

After reading 50+ search results, and testing quite a few of them,
I'm still at:

Code:

Verifying archive integrity... All good.
Uncompressing VirtualBox 5.1.22 Guest Additions for Linux...........
VirtualBox Guest Additions installer
Removing installed version 5.1.22 of VirtualBox Guest Additions...
vboxadd.sh: Stopping VirtualBox Additions.
Copying additional installer modules ...
Installing additional modules ...
vboxadd.sh: Starting the VirtualBox Guest Additions.
Failed to set up service vboxadd, please check the log file
/var/log/VBoxGuestAdditions.log for details.

This is a Virtualbox app which I made last year, and I wanted to enable Guest Additions to fullscreen the window.

I think I have all requirements installed:

- gcc (4.7.1) and friends
- dkms (though I understand VB 5.x doesn't need that anymore)
- Virtualbox 5.1.22
- kernel + headers (4.3.90)

The log mentioned above points to another log. Neither having any useful information.

I'd appreciate any suggestions/ideas.

ponce · 03-01-2018, 10:46 AM

Quote:

Originally Posted by Johncc330

After reading 50+ search results, and testing quite a few of them,
I'm still at:

Code:

Verifying archive integrity... All good.
Uncompressing VirtualBox 5.1.22 Guest Additions for Linux...........
VirtualBox Guest Additions installer
Removing installed version 5.1.22 of VirtualBox Guest Additions...
vboxadd.sh: Stopping VirtualBox Additions.
Copying additional installer modules ...
Installing additional modules ...
vboxadd.sh: Starting the VirtualBox Guest Additions.
Failed to set up service vboxadd, please check the log file
/var/log/VBoxGuestAdditions.log for details.

This is a Virtualbox app which I made last year, and I wanted to enable Guest Additions to fullscreen the window.

I think I have all requirements installed:

- gcc (4.7.1) and friends
- dkms (though I understand VB 5.x doesn't need that anymore)
- Virtualbox 5.1.22
- kernel + headers (4.3.90)

The log mentioned above points to another log. Neither having any useful information.

I'd appreciate any suggestions/ideas.

Hi Johncc330,

sorry, maybe I'm missing something, but why are you posting this question on the Slackware forum?

does you virtual machine run Slackware? which version exactly?

Johncc330 · 03-01-2018, 11:17 AM

Quote:

Originally Posted by ponce

Hi Johncc330,

sorry, maybe I'm missing something, but why are you posting this question on the Slackware forum?

does you virtual machine run Slackware? which version exactly?

Hi Ponce,

Thanks for the reply. I use Slackware at home, but my students mostly use Windows, and/or have a wide variety of Linux flavors installed. So I made a virtual machine with Slackware too, where I installed all tools I need for the course. The version installed is (more or less) Slackware-current, 'current' at about a year back. So kernel is 4.3.90, gcc 4.7.1, etc. which more than covers what I need. I also installed kernel-headers corresponding to the 4.3.90 version.

I posted this here, because 1) it's on Slackware and 2) the installation problem might be slackware-specific as it's not simply apt-get or yum or whatever.

John

ponce · 03-01-2018, 11:38 AM

Hi John, I asked because the last time gcc-4.7.1 was in current is, more or less, six years ago (it's the compiler of Slackware 14.0) and it never shipped kernel 4.3.90...

I haven't tested it myself because I don't have such platform but I think that if you want to install modern virtualbox guest additions and the logs you mention do not have any useful informations the best choice for you is to create a new virtual machine based on slackware 14.2, as the components of your os may be too old.

Johncc330 · 03-01-2018, 11:54 AM

Quote:

Originally Posted by ponce

Hi John, I asked because the last time gcc-4.7.1 was in current is, more or less, six years ago (it's the compiler of Slackware 14.0) and it never shipped kernel 4.3.90...

You're right of course, my apologies. Braincells are fried

I was working from memory...

gcc is 7.1.0

John

AlteredCurrents · 03-04-2018, 09:12 AM

Don't know if this is your problem or not but it has been a problem for me. I'm running the latest Slackware-current in a virtual machine on Windows 7 64bit. I have had to modify the "/etc/init.d/vboxadd" script to keep it from 'punting'.

At least for me, the 'LOG' variable is not setup and it gets an error calling '... /init/vboxadd-x11'.

You could try simply calling 'setup_log' before line #256 in the current vboxadd script.

Code:

# Put the X.Org driver in place.  This is harmless if it is not needed.
# -dep- LOG variable may not be set; make sure it is
setup_log
"${INSTALL_DIR}/init/vboxadd-x11" setup 2>> "${LOG}"
# Install the guest OpenGL drivers.  For now we don't support
# multi-architecture installations

-dep-