Page 1 of 1
Virtualbox won't work after kernel upgrade
Posted: 7. Jun 2008, 18:04
by fbarajas
Hi!
I'm using the closed source Virtualbox 1.6.0 on Ubuntu Linux. I upgraded my kernel ( 2.6.24-19-386 #1 Wed Jun 4 15:54:02 UTC 2008 i686 GNU/Linux) and now VB is not working.
When I try to start a virtual machine, I get:
Code: Select all
VirtualBox kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Re-setup the kernel module by executing '/etc/init.d/vboxdrv setup' as root.
When I run /etc/init.d/vboxdrv setup as root I get:
Code: Select all
# /etc/init.d/vboxdrv setup
* Stopping VirtualBox kernel module * done.
* Recompiling VirtualBox kernel module
* Look at /var/log/vbox-install.log to find out what went wrong
And in "/var/log/vbox-install log" I have:
Code: Select all
#cat /var/log/vbox-install.log
/etc/init.d/vboxdrv: 311: /usr/lib/virtualbox/src/build_in_tmp: not found
What can I do?
Posted: 7. Jun 2008, 18:09
by Sasquatch
Did you install all the needed parts of the Kernel? You need the kernel headers too, not just the Kernel Image. In the kernel headers is the needed source code to build kernel modules.
Upgrading Ubuntu module..
Posted: 7. Jun 2008, 18:14
by pschulz01
Posted: 7. Jun 2008, 18:18
by fbarajas
Sasquatch wrote:Did you install all the needed parts of the Kernel? You
I think I have them installed:
Code: Select all
# apt-cache pkgnames | grep linux-headers-2.6.24-19
linux-headers-2.6.24-19-generic
linux-headers-2.6.24-19-rt
linux-headers-2.6.24-19-server
linux-headers-2.6.24-19-xen
linux-headers-2.6.24-19-386
linux-headers-2.6.24-19-virtual
linux-headers-2.6.24-19
linux-headers-2.6.24-19-openvz
Anything else I can try?
[/code]
Posted: 7. Jun 2008, 20:42
by Sasquatch
fbarajas wrote:Sasquatch wrote:Did you install all the needed parts of the Kernel? You
I think I have them installed:
Code: Select all
# apt-cache pkgnames | grep linux-headers-2.6.24-19
linux-headers-2.6.24-19-generic
linux-headers-2.6.24-19-rt
linux-headers-2.6.24-19-server
linux-headers-2.6.24-19-xen
linux-headers-2.6.24-19-386
linux-headers-2.6.24-19-virtual
linux-headers-2.6.24-19
linux-headers-2.6.24-19-openvz
Anything else I can try?
[/code]
That does not say if it's installed or not. And I wonder how you can see the 2.6.24-19 kernel version. I only see the -18 as latest version. What gives ls /usr/src?
@pschulz01
That is about the OSE version, not the PUEL version you can find on the website as pre-build binaries. You can see the difference because of the error message.
Posted: 7. Jun 2008, 20:47
by skada
Rebuild it for your kernel
Code: Select all
sudo apt-get install virtualbox-ose-source
sudo m-a update
sudo m-a prepare
sudo m-a a-i virtualbox-ose
sudo /etc/init.d/vboxdrv restart
ok start you VBox it should work
Posted: 7. Jun 2008, 21:44
by fbarajas
Sasquatch wrote:
That does not say if it's installed or not. And I wonder how you can see the 2.6.24-19 kernel version. I only see the -18 as latest version. What gives ls /usr/src?
Here's what I have in /usr/src
Code: Select all
# ls /usr/src/
dlink linux-headers-2.6.24-18-generic
linux-headers-2.6.24-16 linux-headers-2.6.24-19
linux-headers-2.6.24-16-generic linux-headers-2.6.24-19-386
linux-headers-2.6.24-17 linux-headers-2.6.24-19-generic
linux-headers-2.6.24-17-386 modules
linux-headers-2.6.24-17-generic rpm
linux-headers-2.6.24-18 vboxdrv-1.6.0
Posted: 7. Jun 2008, 21:49
by fbarajas
skada wrote:Rebuild it for your kernel
Code: Select all
sudo apt-get install virtualbox-ose-source
ok start you VBox it should work
But that will install the OSE version, and I really need USB support for using my Palm Treo. I'd love to use the OSE if it had USB support
Thanks anyway
Posted: 7. Jun 2008, 22:08
by Sasquatch
Ok, in the symlink to vboxdrv-1.6.0, there should be a script that couldn't be found by vboxdrv called 'build_in_tmp'. If you don't have that file, try to reinstall VB. I suggest you update to 1.6.2, as it resolves a lot of issues. With the reinstall, the file should be back.
I noticed that with the new VB, since 1.6.0, it can use DKMS to build the kernel modules. If you don't already have DKMS installed, install it now so the module gets installed every time you update your kernel.
Posted: 7. Jun 2008, 22:37
by fbarajas
Sasquatch wrote: I suggest you update to 1.6.2, as it resolves a lot of issues. With the reinstall, the file should be back.
Thanks a lot!! Upgrading to 1.6.2 fixed the problem!!