[SOLVED] Error message at login on client: "VBoxClient: the VirtualBox kernel service is not running. Exiting."
DebianThis forum is for the discussion of Debian 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.
You don't have to, fortunately, unless you want to see how undeserved my 'guru' status is :-).
In the host system, you need only virtualbox & the extension pack; in each guest you want the guest additions. That's all. You have posted errors that indicated you might have guest additions in the host system, and host system software in the guest (Posts 1 & 11)
Please post the errors showing currently and update us if it's working.
You don't have to, fortunately, unless you want to see how undeserved my 'guru' status is :-).
In the host system, you need only virtualbox & the extension pack; in each guest you want the guest additions. That's all. You have posted errors that indicated you might have guest additions in the host system, and host system software in the guest (Posts 1 & 11)
Please post the errors showing currently and update us if it's working.
Ok. Thanks for sticking by. :-)
During bootup, I see in red text these 2 lines: Failed to start Load Kernel Modules
Failed to start LSB: Virtual Box Additions
At login (on host PC) I get the message; "VBoxClient: the VirtualBox kernel service is not running. Exiting."
When I try to launch a VM in VB, I get these errors [img].
Last edited by linustalman; 02-06-2017 at 08:09 AM.
Distribution: Primarily Deb/Ubuntu, and some CentOS
Posts: 829
Rep:
I get this message in VirtualBox VM's when the VirtualBox software on the host is updated. Usually this will "break" the Additions installation in the guest. So what I do is open up my vm that is complaining with that message, then open a terminal in it, and cd to the directory of the Additions iso. Under the iso directory there is a file called autorun.sh. In that directory I run this command:
Code:
# ./autorun.sh
It will show output saying stuff about dkms and other stuff...
When it's done, reboot your VM and the message should be gone.
Failed to start LSB: Virtual Box Additions
VBoxClient: the VirtualBox kernel service is not running. Exiting.
indicate you have the guest additions installed. Others know better, but I don't think you should have. Whether they're installed or not, something is finding them.
On the VM:
vboxdrv & /dev/vboxdrv belong on the host, not the VM. You seem to have the host software on the guest, and the guest additions on the host.
If I was facing those issues, I would clear everything vbox related. Use locate or slocate and do a case insensitive search. Back up data in the VMs throwing errors and remove them. Reinstall
On host: Virtualbox & extension pack
On guest VMs: Guest additions.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
Quote:
Originally Posted by business_kid
Why is a bit of the Guest Additions wanting to run on the host pc?
because it is a bridge between the two. If the host did not allow open ports it would be irrelevant. However, the host allows these things because sometimes they are needed.
Failed to start LSB: Virtual Box Additions
VBoxClient: the VirtualBox kernel service is not running. Exiting.
indicate you have the guest additions installed. Others know better, but I don't think you should have. Whether they're installed or not, something is finding them.
On the VM:
vboxdrv & /dev/vboxdrv belong on the host, not the VM. You seem to have the host software on the guest, and the guest additions on the host.
If I was facing those issues, I would clear everything vbox related. Use locate or slocate and do a case insensitive search. Back up data in the VMs throwing errors and remove them. Reinstall
On host: Virtualbox & extension pack
On guest VMs: Guest additions.
I reinstalled VB and the extension pack. No joy.
I cannot access any VMs to change anything.
Could you elaborate on 'clear everything vbox related'?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
