How to fix virtualbox startup error: "vboxadd-service ... failed!"
Solution 1:
I faced similar issue. I went through this Installing Guest Additions on Debian. Follow the steps mentioned there. Sometimes missing build-essential module-assistant
packages cause the issue.
Steps
- Login as
root
- Update your APT database with
apt-get update
- Install the latest security updates with
apt-get upgrade
- Install required packages with
apt-get install build-essential module-assistant
- Configure your system for building kernel modules by running
m-a prepare
- Click on Install Guest Additions… from the Devices menu, then run
mount /media/cdrom
- Run
sh /media/cdrom/VBoxLinuxAdditions.run
, and follow the instructions on screen
For me it did the trick. :)
Solution 2:
[disclaimer] this is an old post, written before systemd and the like. The goal is the same, but removing /etc/init.d/
files isn't correct, you should use systemctl disable XXXX
rather than deleting files. [/disclaimer]
[update] I've also posted a solution here for the error Failed to connect to the guest property service
: https://github.com/NixOS/nixops/issues/908#issuecomment-387275731
1) If you run the /media/cdrom/VBoxLinuxAdditions.run
then you'll have some startup scripts in /etc/init.d that doesn't come with Debian default package.
You should get rid of these: ls /etc/*/*vbox*
(remove all rcX.d and init.d files with vbox in the filename).
Important note: You should also look for already compiled modules:
find /lib/modules/ -name "vbox*"
and remove these (based on the assumption that everything was badly installed). If you have multiple files with the same name, that could explain the whole issue (multiple versions of Guest additions are installed).
Or you can simply run: sh /media/cdrom/VBoxLinuxAdditions.run uninstall
.
2) Install only the Debian package virtualbox-guest-dkms
: it seems that VirtualBox doesn't depend on build-essential
and module-assistant
but needs both packages (as stated by @gaborous)! So install all three:
sudo apt-get install build-essential module-assistant virtualbox-guest-dkms
3) To check everything's fine, for example using systemctl
command, just after removing all traces of the CD-Rom install:
- vboxadd-service.service not-found failed failed vboxadd-service.service
- vboxadd.service not-found active exited vboxadd.service
- virtualbox-guest-utils.service loaded active running LSB: VirtualBox Linux Additions
- virtualbox-guest-x11.service loaded active exited LSB: VirtualBox Linux X11 Additions
- virtualbox.service not-found active exited virtualbox.service
After restart:
- virtualbox-guest-utils.service loaded active running LSB: VirtualBox Linux Additions
- virtualbox-guest-x11.service loaded active exited LSB: VirtualBox Linux X11 Additions
4) use systemctl --failed
to list all units that have failed.
And you're back on Debian's wonderful packages :-)
Solution 3:
Make sure that you don't have the multiple copies of the Virtual Box Guest Additions installed. Squeeze will pick up that it is inside a Virtual Box virtual machine and install the 3.x OSE version of the tools automatically.
Solution 4:
After uninstalling the packages Debian automatically added for you, remove the services :
cd /etc/init.d && insserv -r vboxadd vboxadd-service vbox-add-x11
This removed the startup services for me. However, the scripts are still there. If you want to remove them :
cd /etc/init.d && rm vboxadd vboxadd-service vbox-add-x11
BTW: to uninstall the packages : dpkg -l | grep virtual
. Then do apt-get remove --purge <list_of_the_packages>
In my case :
apt-get remove --purge virtualbox-ose-guest-dkms virtualbox-ose-guest-utils virtualbox-ose-guest-x11 && apt-get autoremove && apt-get autoclean
did the trick.
Also, for some reasons, I couldn't have the shared folder with Debian's guest additions. So I had to add the ones from Virtual Box. Add the Cd (should be host key + D, I'm running a french version can't tell the english labels). Then mount the cdrom and run the script with :
mount /media/cdrom && bash /media/cdrom/VBoxLinuxAdditions.run
.
Solution 5:
I fixed the same issue by sudo apt-get install build-essential
(installing dependencies)
and reinstalling guest additions.