How to fix virtualbox startup error: “vboxadd-service … failed!”
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I'm using VirtualBox 4.0.8 with Windows 7 Enterprise 64 bit host and debian 6.0.1a amd64 guest (in CLI mode).
I installed Guest Additions and it seems to work, at least partially, as I have successfully setup a shared folder between host and guest.
However every time I boot the guest, I get the following messages on console:
Starting VirtualBox Guest Addition service ...done.
startpar: services(s) returned failure: vboxadd-service ... failed!
There is no additional error message in any of the logs (checked syslog and VBoxGuestAdditions.log)
Additionally, I'm unable to use shared clipboard between host and guest (it's set to bidirectional, but neither direction seems to work). I assume this might be related to the service start failure.
Any idea how to fix this?
virtualbox guest-additions
add a comment |
I'm using VirtualBox 4.0.8 with Windows 7 Enterprise 64 bit host and debian 6.0.1a amd64 guest (in CLI mode).
I installed Guest Additions and it seems to work, at least partially, as I have successfully setup a shared folder between host and guest.
However every time I boot the guest, I get the following messages on console:
Starting VirtualBox Guest Addition service ...done.
startpar: services(s) returned failure: vboxadd-service ... failed!
There is no additional error message in any of the logs (checked syslog and VBoxGuestAdditions.log)
Additionally, I'm unable to use shared clipboard between host and guest (it's set to bidirectional, but neither direction seems to work). I assume this might be related to the service start failure.
Any idea how to fix this?
virtualbox guest-additions
Possible duplicate of Unable to install VIrtualbox, `"Specify KERN_DIR=<directory>"` -- installing Virtual Box to Debian?
– kenorb
Jun 8 '16 at 15:51
add a comment |
I'm using VirtualBox 4.0.8 with Windows 7 Enterprise 64 bit host and debian 6.0.1a amd64 guest (in CLI mode).
I installed Guest Additions and it seems to work, at least partially, as I have successfully setup a shared folder between host and guest.
However every time I boot the guest, I get the following messages on console:
Starting VirtualBox Guest Addition service ...done.
startpar: services(s) returned failure: vboxadd-service ... failed!
There is no additional error message in any of the logs (checked syslog and VBoxGuestAdditions.log)
Additionally, I'm unable to use shared clipboard between host and guest (it's set to bidirectional, but neither direction seems to work). I assume this might be related to the service start failure.
Any idea how to fix this?
virtualbox guest-additions
I'm using VirtualBox 4.0.8 with Windows 7 Enterprise 64 bit host and debian 6.0.1a amd64 guest (in CLI mode).
I installed Guest Additions and it seems to work, at least partially, as I have successfully setup a shared folder between host and guest.
However every time I boot the guest, I get the following messages on console:
Starting VirtualBox Guest Addition service ...done.
startpar: services(s) returned failure: vboxadd-service ... failed!
There is no additional error message in any of the logs (checked syslog and VBoxGuestAdditions.log)
Additionally, I'm unable to use shared clipboard between host and guest (it's set to bidirectional, but neither direction seems to work). I assume this might be related to the service start failure.
Any idea how to fix this?
virtualbox guest-additions
virtualbox guest-additions
asked Jun 17 '11 at 7:35
András SzepesháziAndrás Szepesházi
5122823
5122823
Possible duplicate of Unable to install VIrtualbox, `"Specify KERN_DIR=<directory>"` -- installing Virtual Box to Debian?
– kenorb
Jun 8 '16 at 15:51
add a comment |
Possible duplicate of Unable to install VIrtualbox, `"Specify KERN_DIR=<directory>"` -- installing Virtual Box to Debian?
– kenorb
Jun 8 '16 at 15:51
Possible duplicate of Unable to install VIrtualbox, `"Specify KERN_DIR=<directory>"` -- installing Virtual Box to Debian?
– kenorb
Jun 8 '16 at 15:51
Possible duplicate of Unable to install VIrtualbox, `"Specify KERN_DIR=<directory>"` -- installing Virtual Box to Debian?
– kenorb
Jun 8 '16 at 15:51
add a comment |
7 Answers
7
active
oldest
votes
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. :)
2
External links can break, in which case your answer wouldn't be useful. For this reason, we ask that you include the essential information within your answer and use the link for attribution and further reading. Can you expand you answer? Thanks.
– fixer1234
Sep 2 '15 at 16:27
3
Thanks to Francisco Tapia for adding the details from the link to this post. As @fixer1234 states, links can die and link only answers are not helpful. The answer as it stands now—with the link plus the instructions—is what a good answer should be.
– JakeGould
Sep 2 '15 at 19:32
1
@JakeGould it shows that 30 seconds of effort to give a answer make a big difference, even if is wrong.
– Francisco Tapia
Sep 2 '15 at 20:04
@FranciscoTapia Considering this answer was posted to a 4+ year old question, we’ll most likely never know if this solved—or had anything to do—with the user’s core issue. But it’s still good information.
– JakeGould
Sep 2 '15 at 23:03
this fixed my tools on Debian 8.5 in VirtualBox 5.1.2
– Jako
Sep 6 '16 at 20:12
|
show 2 more comments
[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 :-)
1
This fixed my issue. However, there wasn't any file to remove withls /etc/*/*vbox*
, but that doesn't matter as installingvirtualbox-guest-dkms
andapt-get install build-essential module-assistant
fixed the issue on its own, I could boot up correctly in my Debian afterward.
– gaborous
Jun 6 '16 at 12:18
7
Note that it's also possible to uninstall the Guest Additions usingsh /opt/VBoxGuestAdditions*/uninstall.sh
– gaborous
Jun 6 '16 at 12:26
add a comment |
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.
I searched for all installed packages via "aptitude search virtualbox", only "virtualbox-ose-guest-dkms" shows up as installed. That should be correct, right?
– András Szepesházi
Jun 27 '11 at 12:25
add a comment |
I fixed the same issue by sudo apt-get install build-essential
(installing dependencies)
and reinstalling guest additions.
add a comment |
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
.
add a comment |
Uninstall virtualbox-ose
and reinstall all VirtualBox Debian packages with:
aptitude search virtualbox
add a comment |
Un-checking the Guest Additions iso from Devices may help you - it did for me:
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f298367%2fhow-to-fix-virtualbox-startup-error-vboxadd-service-failed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
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. :)
2
External links can break, in which case your answer wouldn't be useful. For this reason, we ask that you include the essential information within your answer and use the link for attribution and further reading. Can you expand you answer? Thanks.
– fixer1234
Sep 2 '15 at 16:27
3
Thanks to Francisco Tapia for adding the details from the link to this post. As @fixer1234 states, links can die and link only answers are not helpful. The answer as it stands now—with the link plus the instructions—is what a good answer should be.
– JakeGould
Sep 2 '15 at 19:32
1
@JakeGould it shows that 30 seconds of effort to give a answer make a big difference, even if is wrong.
– Francisco Tapia
Sep 2 '15 at 20:04
@FranciscoTapia Considering this answer was posted to a 4+ year old question, we’ll most likely never know if this solved—or had anything to do—with the user’s core issue. But it’s still good information.
– JakeGould
Sep 2 '15 at 23:03
this fixed my tools on Debian 8.5 in VirtualBox 5.1.2
– Jako
Sep 6 '16 at 20:12
|
show 2 more comments
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. :)
2
External links can break, in which case your answer wouldn't be useful. For this reason, we ask that you include the essential information within your answer and use the link for attribution and further reading. Can you expand you answer? Thanks.
– fixer1234
Sep 2 '15 at 16:27
3
Thanks to Francisco Tapia for adding the details from the link to this post. As @fixer1234 states, links can die and link only answers are not helpful. The answer as it stands now—with the link plus the instructions—is what a good answer should be.
– JakeGould
Sep 2 '15 at 19:32
1
@JakeGould it shows that 30 seconds of effort to give a answer make a big difference, even if is wrong.
– Francisco Tapia
Sep 2 '15 at 20:04
@FranciscoTapia Considering this answer was posted to a 4+ year old question, we’ll most likely never know if this solved—or had anything to do—with the user’s core issue. But it’s still good information.
– JakeGould
Sep 2 '15 at 23:03
this fixed my tools on Debian 8.5 in VirtualBox 5.1.2
– Jako
Sep 6 '16 at 20:12
|
show 2 more comments
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. :)
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. :)
edited Oct 15 '17 at 16:50
Community♦
1
1
answered Sep 2 '15 at 16:04
Mithilesh Kumar MahapatraMithilesh Kumar Mahapatra
18113
18113
2
External links can break, in which case your answer wouldn't be useful. For this reason, we ask that you include the essential information within your answer and use the link for attribution and further reading. Can you expand you answer? Thanks.
– fixer1234
Sep 2 '15 at 16:27
3
Thanks to Francisco Tapia for adding the details from the link to this post. As @fixer1234 states, links can die and link only answers are not helpful. The answer as it stands now—with the link plus the instructions—is what a good answer should be.
– JakeGould
Sep 2 '15 at 19:32
1
@JakeGould it shows that 30 seconds of effort to give a answer make a big difference, even if is wrong.
– Francisco Tapia
Sep 2 '15 at 20:04
@FranciscoTapia Considering this answer was posted to a 4+ year old question, we’ll most likely never know if this solved—or had anything to do—with the user’s core issue. But it’s still good information.
– JakeGould
Sep 2 '15 at 23:03
this fixed my tools on Debian 8.5 in VirtualBox 5.1.2
– Jako
Sep 6 '16 at 20:12
|
show 2 more comments
2
External links can break, in which case your answer wouldn't be useful. For this reason, we ask that you include the essential information within your answer and use the link for attribution and further reading. Can you expand you answer? Thanks.
– fixer1234
Sep 2 '15 at 16:27
3
Thanks to Francisco Tapia for adding the details from the link to this post. As @fixer1234 states, links can die and link only answers are not helpful. The answer as it stands now—with the link plus the instructions—is what a good answer should be.
– JakeGould
Sep 2 '15 at 19:32
1
@JakeGould it shows that 30 seconds of effort to give a answer make a big difference, even if is wrong.
– Francisco Tapia
Sep 2 '15 at 20:04
@FranciscoTapia Considering this answer was posted to a 4+ year old question, we’ll most likely never know if this solved—or had anything to do—with the user’s core issue. But it’s still good information.
– JakeGould
Sep 2 '15 at 23:03
this fixed my tools on Debian 8.5 in VirtualBox 5.1.2
– Jako
Sep 6 '16 at 20:12
2
2
External links can break, in which case your answer wouldn't be useful. For this reason, we ask that you include the essential information within your answer and use the link for attribution and further reading. Can you expand you answer? Thanks.
– fixer1234
Sep 2 '15 at 16:27
External links can break, in which case your answer wouldn't be useful. For this reason, we ask that you include the essential information within your answer and use the link for attribution and further reading. Can you expand you answer? Thanks.
– fixer1234
Sep 2 '15 at 16:27
3
3
Thanks to Francisco Tapia for adding the details from the link to this post. As @fixer1234 states, links can die and link only answers are not helpful. The answer as it stands now—with the link plus the instructions—is what a good answer should be.
– JakeGould
Sep 2 '15 at 19:32
Thanks to Francisco Tapia for adding the details from the link to this post. As @fixer1234 states, links can die and link only answers are not helpful. The answer as it stands now—with the link plus the instructions—is what a good answer should be.
– JakeGould
Sep 2 '15 at 19:32
1
1
@JakeGould it shows that 30 seconds of effort to give a answer make a big difference, even if is wrong.
– Francisco Tapia
Sep 2 '15 at 20:04
@JakeGould it shows that 30 seconds of effort to give a answer make a big difference, even if is wrong.
– Francisco Tapia
Sep 2 '15 at 20:04
@FranciscoTapia Considering this answer was posted to a 4+ year old question, we’ll most likely never know if this solved—or had anything to do—with the user’s core issue. But it’s still good information.
– JakeGould
Sep 2 '15 at 23:03
@FranciscoTapia Considering this answer was posted to a 4+ year old question, we’ll most likely never know if this solved—or had anything to do—with the user’s core issue. But it’s still good information.
– JakeGould
Sep 2 '15 at 23:03
this fixed my tools on Debian 8.5 in VirtualBox 5.1.2
– Jako
Sep 6 '16 at 20:12
this fixed my tools on Debian 8.5 in VirtualBox 5.1.2
– Jako
Sep 6 '16 at 20:12
|
show 2 more comments
[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 :-)
1
This fixed my issue. However, there wasn't any file to remove withls /etc/*/*vbox*
, but that doesn't matter as installingvirtualbox-guest-dkms
andapt-get install build-essential module-assistant
fixed the issue on its own, I could boot up correctly in my Debian afterward.
– gaborous
Jun 6 '16 at 12:18
7
Note that it's also possible to uninstall the Guest Additions usingsh /opt/VBoxGuestAdditions*/uninstall.sh
– gaborous
Jun 6 '16 at 12:26
add a comment |
[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 :-)
1
This fixed my issue. However, there wasn't any file to remove withls /etc/*/*vbox*
, but that doesn't matter as installingvirtualbox-guest-dkms
andapt-get install build-essential module-assistant
fixed the issue on its own, I could boot up correctly in my Debian afterward.
– gaborous
Jun 6 '16 at 12:18
7
Note that it's also possible to uninstall the Guest Additions usingsh /opt/VBoxGuestAdditions*/uninstall.sh
– gaborous
Jun 6 '16 at 12:26
add a comment |
[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 :-)
[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 :-)
edited Mar 8 at 10:00
answered Apr 28 '15 at 3:49
YvanYvan
18114
18114
1
This fixed my issue. However, there wasn't any file to remove withls /etc/*/*vbox*
, but that doesn't matter as installingvirtualbox-guest-dkms
andapt-get install build-essential module-assistant
fixed the issue on its own, I could boot up correctly in my Debian afterward.
– gaborous
Jun 6 '16 at 12:18
7
Note that it's also possible to uninstall the Guest Additions usingsh /opt/VBoxGuestAdditions*/uninstall.sh
– gaborous
Jun 6 '16 at 12:26
add a comment |
1
This fixed my issue. However, there wasn't any file to remove withls /etc/*/*vbox*
, but that doesn't matter as installingvirtualbox-guest-dkms
andapt-get install build-essential module-assistant
fixed the issue on its own, I could boot up correctly in my Debian afterward.
– gaborous
Jun 6 '16 at 12:18
7
Note that it's also possible to uninstall the Guest Additions usingsh /opt/VBoxGuestAdditions*/uninstall.sh
– gaborous
Jun 6 '16 at 12:26
1
1
This fixed my issue. However, there wasn't any file to remove with
ls /etc/*/*vbox*
, but that doesn't matter as installing virtualbox-guest-dkms
and apt-get install build-essential module-assistant
fixed the issue on its own, I could boot up correctly in my Debian afterward.– gaborous
Jun 6 '16 at 12:18
This fixed my issue. However, there wasn't any file to remove with
ls /etc/*/*vbox*
, but that doesn't matter as installing virtualbox-guest-dkms
and apt-get install build-essential module-assistant
fixed the issue on its own, I could boot up correctly in my Debian afterward.– gaborous
Jun 6 '16 at 12:18
7
7
Note that it's also possible to uninstall the Guest Additions using
sh /opt/VBoxGuestAdditions*/uninstall.sh
– gaborous
Jun 6 '16 at 12:26
Note that it's also possible to uninstall the Guest Additions using
sh /opt/VBoxGuestAdditions*/uninstall.sh
– gaborous
Jun 6 '16 at 12:26
add a comment |
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.
I searched for all installed packages via "aptitude search virtualbox", only "virtualbox-ose-guest-dkms" shows up as installed. That should be correct, right?
– András Szepesházi
Jun 27 '11 at 12:25
add a comment |
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.
I searched for all installed packages via "aptitude search virtualbox", only "virtualbox-ose-guest-dkms" shows up as installed. That should be correct, right?
– András Szepesházi
Jun 27 '11 at 12:25
add a comment |
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.
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.
answered Jun 25 '11 at 18:12
D'NabreD'Nabre
1612
1612
I searched for all installed packages via "aptitude search virtualbox", only "virtualbox-ose-guest-dkms" shows up as installed. That should be correct, right?
– András Szepesházi
Jun 27 '11 at 12:25
add a comment |
I searched for all installed packages via "aptitude search virtualbox", only "virtualbox-ose-guest-dkms" shows up as installed. That should be correct, right?
– András Szepesházi
Jun 27 '11 at 12:25
I searched for all installed packages via "aptitude search virtualbox", only "virtualbox-ose-guest-dkms" shows up as installed. That should be correct, right?
– András Szepesházi
Jun 27 '11 at 12:25
I searched for all installed packages via "aptitude search virtualbox", only "virtualbox-ose-guest-dkms" shows up as installed. That should be correct, right?
– András Szepesházi
Jun 27 '11 at 12:25
add a comment |
I fixed the same issue by sudo apt-get install build-essential
(installing dependencies)
and reinstalling guest additions.
add a comment |
I fixed the same issue by sudo apt-get install build-essential
(installing dependencies)
and reinstalling guest additions.
add a comment |
I fixed the same issue by sudo apt-get install build-essential
(installing dependencies)
and reinstalling guest additions.
I fixed the same issue by sudo apt-get install build-essential
(installing dependencies)
and reinstalling guest additions.
edited Nov 16 '16 at 3:07
answered Nov 10 '16 at 0:47
llllllllllllllll
112
112
add a comment |
add a comment |
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
.
add a comment |
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
.
add a comment |
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
.
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
.
answered Apr 10 '15 at 14:18
Sumi StraessleSumi Straessle
1011
1011
add a comment |
add a comment |
Uninstall virtualbox-ose
and reinstall all VirtualBox Debian packages with:
aptitude search virtualbox
add a comment |
Uninstall virtualbox-ose
and reinstall all VirtualBox Debian packages with:
aptitude search virtualbox
add a comment |
Uninstall virtualbox-ose
and reinstall all VirtualBox Debian packages with:
aptitude search virtualbox
Uninstall virtualbox-ose
and reinstall all VirtualBox Debian packages with:
aptitude search virtualbox
edited Jun 8 '16 at 12:20
kenorb
11.7k1580118
11.7k1580118
answered Apr 12 '13 at 10:30
hackensolohackensolo
1
1
add a comment |
add a comment |
Un-checking the Guest Additions iso from Devices may help you - it did for me:
add a comment |
Un-checking the Guest Additions iso from Devices may help you - it did for me:
add a comment |
Un-checking the Guest Additions iso from Devices may help you - it did for me:
Un-checking the Guest Additions iso from Devices may help you - it did for me:
edited Feb 14 '18 at 1:39
Twisty Impersonator
18.8k1468101
18.8k1468101
answered Feb 14 '18 at 1:05
Dr. AlexanderDr. Alexander
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f298367%2fhow-to-fix-virtualbox-startup-error-vboxadd-service-failed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Possible duplicate of Unable to install VIrtualbox, `"Specify KERN_DIR=<directory>"` -- installing Virtual Box to Debian?
– kenorb
Jun 8 '16 at 15:51