Error message at login on client: "VBoxClient: the VirtualBox kernel service is not running. Exiting."
Hi.
I get this error message after boot up when my desktop loads on my main PC (not inside VirtualBox): "VBoxClient: the VirtualBox kernel service is not running. Exiting." I have VB installed with a few VMs and the shared clipboard works for Linux Mint 17.3 and Ubuntu MATE 16.04 which I have installed inside VirtualBox. Is there a fix for this? I'm running Debian 8 Jessie x64. Thanks. |
What kernel modules are loaded in the main machine? As root
Code:
lsmod |grep vbox |
Quote:
Here's the output: Code:
vboxpci 24576 0 |
Same modules as I have. Have you the guest additions loaded on the host, by any chance? VBoxClient appears to be in the guest additions and run on the guest, not the main machine.
|
Quote:
Do you refer to the package 'virtualbox-guest-additions-iso'? I do not have it installed on my host machine. Should I install it? |
No, I don't think so. You install the extension pack on your host, and the guest additions on your guest. Try this one line at a time:
Code:
which VBoxClient Code:
find -type l |xargs ls -l |less |
Have you recently updated the kernel for your host machine? If so, did you rebuild the VBox kernel for the new kernel.
I have received that message on Slackware under that circumstance and fixed it by doing rebuilding the VBox kernel against the new system kernel. Slackware uses a BSD style init system, so the mechanics of how to do it would be different, but it would be something to check into. This should help: https://wiki.debian.org/VirtualBox#K...8rc.3D-1908.29 |
To business_kid & frankbell.
The kernel may have been updated. My current version is: 4.8.0-0.bpo.2-amd64 Since my VMs work fine, I may just let this issue alone as it does not seem to be causing any problems other than the error message upon logging into host machine. |
Thanks for the update. Please let us know if you get to the bottom of it.
|
|
During bootup this morn, I noticed in read text 2 lines (not one after another):
They were something like: Code:
Failed to start Load Kernel Modules |
1 Attachment(s)
I got this error when I went to launch a VM in VirtualBox [img].
I tried: Code:
sudo 'modprobe vboxdrv' Code:
# 'modprobe vboxdrv' The output was: Code:
modprobe: FATAL: Module vboxdrv not found. |
I have recently battled with this and probably made every conceivable mistake.
http://www.linuxquestions.org/questi...ox-4175597655/ http://www.linuxquestions.org/questi...te-4175596144/ vboxdrv.ko runs on the host, not the guest. The "error" was your command. Have you virtualbox installed on the guest as well? You don't need anyvirtualbox stuff in the guest to get booting. You need the guest additions for extra features, usb etc. |
I recall now I had this issue in the past when I ran Linux Mint.
I had these noted in a text file: Code:
sudo apt-get install build-essential module-assistant Code:
sudo /etc/init.d/vboxdrv setup Code:
sudo modprobe vboxdrv |
Quote:
|
All times are GMT -5. The time now is 12:04 PM. |