[Wirezfree]

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.

[Coastie]

Moved - might have been hijacking post.  :-[

[greenisland]

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.

[valtam]

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

[greenisland]

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.

[valtam]

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

[torreydale]

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.

[stevedat]

To me, I got problem with usb on Windows XP running on VirtualBox although I installed extension.
Any ideas, pls.

[valtam]

There is VB guide in the Help Manual. Run through that carefully.

Sent from my Nexus 6 using Tapatalk

[firenice03]

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

Code:

sudo apt-get autoclean

once cleaned the Autoremove Packages ran fine...

Reboot and the system WITHOUT VBox no longer gave the kernel error 


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.