Linux Lite Forums
Software - Support => Other => Topic started by: Josef on November 25, 2015, 08:02:36 PM
-
Some updates in the packages from Wednesday, 26th Nov caused that VirtualBox aborts during startup of e.g. a WinXP machine without any warnings or comment...!?
Please let me know what I can do from my end to fix or at least find a workaround!
-
What version of Virtualbox are you running..??, look under "Help > About"
I'm running 5.0.10 r104061
I just checked what updates are available, but I did not install.
There are no updates for Version 5.0.10, but there are 3 for Version-4.
19 : Name: virtualbox-guest-x11 INSTALLED: 4.3.10-dfsg-1ubuntu5 AVAILABLE: 4.3.34-dfsg-1+deb8u1ubuntu1.14.04.1
20 : Name: virtualbox-guest-utils INSTALLED: 4.3.10-dfsg-1ubuntu5 AVAILABLE: 4.3.34-dfsg-1+deb8u1ubuntu1.14.04.1
21 : Name: virtualbox-guest-dkms INSTALLED: 4.3.10-dfsg-1ubuntu5 AVAILABLE: 4.3.34-dfsg-1+deb8u1ubuntu1.14.04.1
I checked in synaptic, I only have a "green dot" installed for Virtualbox-5.0 ,
So why is it offering updates for Version-4 ..??
-
I updated earlier saw there were VBox updates (running 4.3.34) I shut down, when restarting got a virtualbox kernel not running message..
I am able to launch the VM fine(FreeNAS VM)...
If it helps I can post the updates... Just point me to the log file :)
-
@firenice03
Is the error coming in the Guest when you open it..??
or appearing on the host..??
You can see logs by right clicking on your "NAS VM" in the Virtualbox main GUI screen and click on "Show Logs"
Have you updated the VM's "Guest Additions (https://www.virtualbox.org/manual/ch04.html)" after this update, look in the Install section.
the Virtualbox Guest Additions and the Virtualbox Host versions need to match.?
-
Thus far the VM was fine.. The only updates ran were for LL updates (from Lite Control Center). Additions were probably added at time of initial install; versions match under extensions
Not sure if the error was for the reboot after update, I'll reboot again..
The VM seems fine thou..
Was suggesting if any wanted to know what LL updates for VBox 4.3 were installed..
I'll reboot and update :)
Update.. The message is:
VBoxClient: the VirtualBox kernel service is not running. Exiting
Not sure if its informational - as the VM ran fine or how long the message has been occurring as I don't reboot often :)
-
In addition to updating the guest additions, you may want to consider updating the Extensions Pack to match the version of your VirtualBox. You can find it at this link (https://www.virtualbox.org/wiki/Downloads).
Then from the VirtualBox Manager window, click on File and Preferences. There you'll see a section on Extensions. From there you can add the Extensions Pack package that you downloaded.
-
@firenice03.
O.K, When you do a LL updates it "also" pulls Virtuabox updates, if there are any.
The ones I listed are also part of the the current LL updates.
Looking in the log file sometimes actually contains a suggestion on how to fix.??
@torreydale.
Good spot, I forgot about the extensions pack.
-
Thus far the VM was fine.. The only updates ran were for LL updates (from Lite Control Center). Additions were probably added at time of initial install; versions match under extensions
Not sure if the error was for the reboot after update, I'll reboot again..
The VM seems fine thou..
Was suggesting if any wanted to know what LL updates for VBox 4.3 were installed..
I'll reboot and update :)
Update.. The message is:
VBoxClient: the VirtualBox kernel service is not running. Exiting
Not sure if its informational - as the VM ran fine or how long the message has been occurring as I don't reboot often :)
I had the same message.
As I didn't know enough about what I was doing I simply purged VBox, but after a reboot the issue remained. I looked in Synaptic for Vbox related stuff that were remaining and found 3 entries for VKMS, after removing these the issue went away. So would that mean the issue lies between VKMS and the update? I dunno, but maybe it's a clue.
Anyway, although hardly scientific, just Installing Vbox from their homepage along with the extensions again fixed the issue for me.
-
Thanks all, I'll try the extensions and guest additions see whats what... Thought maybe the OP and myself had similar issues.
Happy Thanksgiving
:)
-
In the process to assemble all information requested by you I noticed your quick response coming in. So I checked my system and found;
- Oracle VM VirtualBox - 4.3.34 Ubuntu r104062
BUT
- Extension Pack - 4.3.10
was limping behind...
I updated the Extension Pack to 4.3.34, a BIG THANK YOU to 'torreydale', and YES, I regained access to my business archive.
Thank you all for your help to solve my problem with VM VirtualBox, I really appreciate!!!
-
Glad it's all sorted :)
again, good spot torreydale
I must remember:
1. Update Virtualbox App
2. Update Extensions pack
3. Update Guest Additions in each guest.
-
Moved - might have been hijacking post. :-[
-
OK I just had the same problem - very disconcerting - I thought I had somehow corrupted my virtualbox appliance.
Anyway, I solved the problem by uninistalling everything and downloading the latest virtualbox program and extension pack from the virtualbox website.
But now I am confused. Is it not sufficient to keep updating through the main linux lite updater? How did I get left behind at version 4.3 if the latest is version 5?
thanks for any info so I can avoid this in the future.
-
No need to uninstall anything. The extension pack is separate and does not come from updates, theres no way of knowing that virtualbox won't load vm's until you get an error. If you get an error, simply get the correct version of the extension pack from here - https://www.virtualbox.org/wiki/Downloads
-
Thank you Jerry. What about the issue of getting the latest (version 5) of virtualbox itself? I have been doing regular updates but I don't think that it upgraded itself to version 5 til I went to the virtualbox website.
-
I advise against going outside the repos unless you are competent enough to get out of a bad situation. I still run v4 and have 9 vm's no issues.
Sent from my Nexus 6 using Tapatalk
-
I concur. I tried version 5 because it looked like the bidirectional Shared Clipboard and Drag and Drop would work better. I still had trouble with it, though. So I reverted back to the version in the repository, and I learned to use a shared folder between my host and the VMs. That works good enough for me.
-
To me, I got problem with usb on Windows XP running on VirtualBox although I installed extension.
Any ideas, pls.
-
There is VB guide in the Help Manual. Run through that carefully.
Sent from my Nexus 6 using Tapatalk
-
Hey all, been away for a bit but I got around to looking at this today.. Now I have 2 LL boxes 1 with VBox other without..
Both were giving the kernel message ..
On the system WITHOUT VBox as AFMS suggested from another post SEE BELOW
I removed the additional guest packages in Synaptic.. Rebooted same same, message continued..
I tried Lite Tweaks: Autoremove Packages and clean Package Cache and config files..
- Autoremove Packages ERRORed and I needed to run from terminal sudo apt-get autocleanonce cleaned the Autoremove Packages ran fine...
Reboot and the system WITHOUT VBox no longer gave the kernel error :D
The system WITH VBox did the same Lite Tweaks as above and installed the extension pack from the wiki...
VBox Kernel Service is Not Running message continues... Message in on LL right after logging in after a reboot - - prior to launching any app..
VBox works fine - just gives the error...
Checked all component versions match 4.3.34.
I do not use VirtualBox but also get the notification message. With Synaptic manager I removed all Virtual Box related packages and then reboot. This did not work. Then I saw some residual packages in Synaptic. I then used Lite Tweaks to autoremove packages, clean package cache and clean residual config files. After that and a reboot the message was gone.
I am not a computer expert but it worked and maybe this is of use for people who do not use VirtualBox at all and get that anoying message.
Greetings,
Ton.
-
I have just done 5 X LL updates, all offered yet another update to Virtualbox
After this update, "None" are showing the VBox Kernel message..