Virtualbox requires a reboot after install to work

Bug #153148 reported by Conrad Knauer
2
Affects Status Importance Assigned to Milestone
virtualbox-ose-modules (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After installing virtualbox-ose and virtualbox-ose-modules-2.6.22-14-generic, adding myself to the "vboxusers" group and attempting to run Damn Small Linux in it, Virtualbox didn't work right, giving me the error:

VirtualBox kernel driver not installed. The vboxdrv kernel module was either not loaded or /dev/vboxdrv was not created for some reason. Please install the virtualbox-ose-modules package for your kernel and execute '/etc/init.d/vboxdrv start' as root.
VBox status code: -1908 (VERR_VM_DRIVER_NOT_INSTALLED).

Result Code:
0x80004005
Component:
Console
Interface:
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}

Indeed, /dev/vboxdrv did not exist. A reboot later and it did and thus worked. I don't recall the PUEL edition doing this; shouldn't the OSE version just work right away, without the need to reboot or manually run a command? (can't it do it automatically as part of the install?)

Revision history for this message
Conrad Knauer (atheoi) wrote :

I tried uninstalling Virtualbox OSE and rebooted; this removed /dev/vboxdrv
Then I reinstalled the two packages and it was suddenly there WITHOUT needing to reboot.
Dunno how I got it to not work the first time, but it seems to work now, so I'm going to mark my bug as invalid ^_-;

Changed in virtualbox-ose-modules:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.