Problem with VirtualBox after upgrading kernel to 4.5.2

donald3.heckel · 04-29-2016, 01:54 PM

Quote:

Originally Posted by donald3.heckel

Update:

It's showing this for the other modules too?

If all else fails, you could try a Virtualbox reinstall.

Code:

sudo apt-get autoremove virtualbox
sudo apt-get purge virtualbox

And instead of using apt-get,

Download:

http://download.virtualbox.org/virtu...inux_amd64.run

And then run:

Code:

chmod +x VirtualBox-5.0.20-106931-Linux_amd64.run
sudo ./VirtualBox-5.0.20-106931-Linux_amd64.run

That should rebuild the kernel modules. Be sure to keep the aforementioned modules in your /etc/modules.

Sincerely,

donald3.heckel

You're welcome

hydrurga · 04-29-2016, 01:57 PM

Quote:

Originally Posted by donald3.heckel

You're welcome

Ok. Before I get to it, if I carry out

sudo apt-get autoremove virtualbox
sudo apt-get purge virtualbox

how will this affect my current images (of which there are several) once I've reinstalled VirtualBox? Will I have to reconnect them all?

donald3.heckel · 04-29-2016, 01:59 PM

Quote:

Originally Posted by hydrurga

I'll get there. I'll try the module method you mentioned before the fallback reinstall one. However, vboxdrv isn't installed despite dpkg-l showing that virtualbox-5.0 is installed.

I guess vboxdrv is being faulty. I believe if you installed from source or tried loading your modules with no effect, I guess your reinstall might be the only option.

Info:

About the /etc/modules, it will load those modules on boot if all goes well.

Sincerely,
donald3.heckel

donald3.heckel · 04-29-2016, 02:04 PM

Your Virtualbox images should be unaffected. When you reinstall, be sure to add them back in.

If you are too concerned, I suggest you temporarily move them out of the way say ~/vboxBaks for example.

Sincerely,

donald3.heckel

donald3.heckel · 04-29-2016, 02:16 PM

Let me know how it goes.

Sincerely,

donald3.heckel

hydrurga · 04-29-2016, 02:27 PM

OK, I uninstalled, purged and installed VirtualBox exactly as you suggested. The result of the installation was:

Code:

Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.............
VirtualBox Version 5.0.20 r106931 (2016-04-28T13:33:21Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
Building the VirtualBox kernel modules
Error! Bad return status for module build on kernel: 4.5.2-040502-generic (x86_64)
Consult /var/lib/dkms/vboxhost/5.0.20/build/make.log for more information.

VirtualBox has been installed successfully.

You will find useful information about using VirtualBox in the user manual
  /opt/VirtualBox/UserManual.pdf
and in the user FAQ
  http://www.virtualbox.org/wiki/User_FAQ

We hope that you enjoy using VirtualBox.

Then, I experience exactly the same problem in trying to launch a VirtualBox client as before.

The build log complains about the lack of support for -fstack-protector-strong as before.

donald3.heckel · 04-29-2016, 02:30 PM

Ahhh okay.

Assuming the module loading won't work,

Post the output of uname -r.

Sincerely,

donald3.heckel

donald3.heckel · 04-29-2016, 02:31 PM

Quote:

Originally Posted by donald3.heckel

Ahhh okay.

Assuming the module loading won't work,

Post the output of uname -r.

Sincerely,

donald3.heckel

Make sure you have them loaded. If it does not work, let me know the output of your uname -r.

hydrurga · 04-29-2016, 02:43 PM

Quote:

Originally Posted by donald3.heckel

Make sure you have them loaded. If it does not work, let me know the output of your uname -r.

modprobe reports all modules missing, despite the contents of /etc/modules being

Code:

lp
rtc
vboxdrv
vboxpci
vbox-host-dkms
vboxnetadp
vboxnetflt

and a reboot having taken place since that file was edited.

uname -r gives

4.5.2-040502-generic

hydrurga · 04-29-2016, 03:06 PM

Donald, thanks for all your help, but I'm going to restore my previous o/s from backup (I tried rebooting into the older kernel but VirtualBox is now balking for another reason - it will be cleaner to just restore things as they were). I reckon my experiment with upgrading my kernel is at an end...

donald3.heckel · 04-29-2016, 04:43 PM

No problem. I hope you found this useful. At least we tried!

Sincerely,

donald3.heckel

BW-userx · 04-29-2016, 06:39 PM

Quote:

Originally Posted by hydrurga

(more info)

On running dpkg-reconfigure virtualbox-5.0, the result is:

Code:

addgroup: The group `vboxusers' already exists as a system group. Exiting.
Stopping VirtualBox kernel modules ...done.
Uninstalling old VirtualBox DKMS kernel modulesError! Could not locate dkms.conf file.
File:  does not exist.
 ...done.
Trying to register the VirtualBox kernel modules using DKMSError! Bad return status for module build on kernel: 4.5.2-040502-generic (x86_64)
Consult /var/lib/dkms/vboxhost/5.0.20/build/make.log for more information.
 ...failed!
  (Failed, trying without DKMS)
Recompiling VirtualBox kernel modules ...failed!
  (Look at /var/log/vbox-install.log to find out what went wrong)

/var/log/vbox-install.log is quite complex but the main error seems to be that -fstack-protector-strong is not recognised as a command line option by gcc.

do you have DKMS installed???
header files, and all that other stuff it needs to build what it needs to?

I did a remove everything, but my files with installes in them. then reinstalled it, let it pull in the dependices and do its thing, it saved me a lot of problems and such.

mine just picks the installed VirtOS's when its reinstlled due to the config dir it puts in /home/user/xxx

you might have to twik it a little to get them working, but you do not lose anything. I didn't anyways.