[Bug 253802] Re: virtual box modules not upgraded with kernel. amd64
Dan Ratner
dr_public at lovetohack.org
Wed Apr 15 16:25:53 UTC 2009
I don't know if this is related or not but I upgraded to Jaunty from
Intrepid and subsequently, the VB gave errors:
VERR_VM_DRIVER_NOT_INSTALLED (rc=-1908)
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv.
Re-setup the kernel module by executing
/etc/init.d/vboxdrv setup
as root. Users of Ubuntu or Fedora should install the DKMS package at first. This package keeps track of Linux kernel
changes and recompiles the vboxdrv kernel module if necessary.
After confirming that DKMS was setup, I ran the set up as suggested and
it errored out almost immediately:
* Stopping VirtualBox kernel module * done.
* Recompiling VirtualBox kernel module
* Look at /var/log/vbox-install.log to find out what went wrong
So I looked at that log file and it contained a single line:
/etc/init.d/vboxdrv: 342:
/usr/share/virtualbox/src/vboxdrv/build_in_tmp: not found
So I d/l the new .deb from the VB website and THAT wouldn't install
either. I ultimately had to completely uninstall via Synaptic and then
re-install via the .deb to get the fully functional
I don't know if this is a Ubuntu issue or a VB issue, but it is an
annoyance at the very least.
I was using VirtualBox 2.1.4 (not OSE ver).
--
virtual box modules not upgraded with kernel. amd64
https://bugs.launchpad.net/bugs/253802
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
More information about the universe-bugs
mailing list