| View previous topic :: View next topic |
| Author |
Message |
pjgat09
n00b
Joined: 26 Jan 2007
Posts: 19
|
 Posted: Thu Apr 23, 2009 8:22 pm Post subject: Virtual machines in Virtualbox-bin-2.2.0 don't run[RESOLVED] |
 |
|
I recently updated to virtualbox-bin-2.2.0, and all of my virtual machines fail to start, first with an error of
| Code: | Failed to open a session for the virtual machine Windows XP.
Virtual machine 'Windows XP' has terminated unexpectedly during startup. |
followed by
| Code: | Kernel driver not accessible (rc=-1909)
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, Fedora or Mandriva should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary. |
The driver is loaded:
| Code: |
pjgat09-laptop pjgat09 # lsmod
Module Size Used by
vboxnetflt 68904 0
vboxdrv 93480 1 vboxnetflt
|
And /dev/vboxdrv exists:
| Code: |
pjgat09-laptop pjgat09 # ls -l /dev/vboxdrv
crw-rw---- 1 root vboxusers 10, 59 2009-04-23 15:39 /dev/vboxdrv
|
Most of my searching has told me this usually means the user is not in the vboxusers group, however I am:
| Code: |
pjgat09-laptop pjgat09 # groups pjgat09
wheel uucp audio cdrom video usb users portage cron plugdev games vboxusers fingerprint dropbox wireshark pjgat09
|
It also seems I don't have /etc/init.d/vboxdrv to run the setup the error suggested:
| Code: |
pjgat09-laptop pjgat09 # ls /etc/init.d/vb*
ls: cannot access /etc/init.d/vb*: No such file or directory
|
I've tried logging out and back in, removing the drivers and re-inserting, re-emerging both virtualbox-bin and virtualbox followed by removing/re-inserting the drivers again, all with no luck. What do I need to do to get my virtual machines running again? I am running the 2.6.27-gentoo-r8 kernel. Any help would be great. Thanks.
Last edited by pjgat09 on Fri Apr 24, 2009 6:02 pm; edited 1 time in total |
|
| Back to top |
|
 |
yabbadabbadont
Advocate
Joined: 14 Mar 2003
Posts: 4791
Location: 2 exits past crazy
|
| Posted: Thu Apr 23, 2009 8:50 pm Post subject: |
|
|
It sounds like you did, but just to check, have you re-emerged virtualbox-modules and rebooted afterwards?
Also, is the version of the installed virtualbox-modules the same as virtualbox-bin or OSE? |
|
| Back to top |
|
|
pjgat09
n00b
Joined: 26 Jan 2007
Posts: 19
|
| Posted: Thu Apr 23, 2009 10:29 pm Post subject: |
|
|
I was pretty sure I had rebooted, but I re-emerged virtualbox-modules again and rebooted just to be sure. Still no luck.
Both virtualbox-bin and virtualbox-modules are the same version, 2.2.0. |
|
| Back to top |
|
|
pjgat09
n00b
Joined: 26 Jan 2007
Posts: 19
|
| Posted: Fri Apr 24, 2009 6:02 pm Post subject: |
|
|
I updated to kernel 2.6.28-gentoo-r5 today, rebuilt all of my seperate modules (including virtualbox-modules). After rebooting into the new kernel, I tried to start the VirtualBox management window, and only got a blank window. I tried starting it from command line, with no output and again only a blank window. After a few tries, the window loaded correctly, and my virtual machines start no problem.
Seems to be working for now, but I'm not sure what caused the original problem. |
|
| Back to top |
|
|
kasim
n00b
Joined: 17 Feb 2007
Posts: 31
|
| Posted: Sun Apr 26, 2009 5:49 am Post subject: |
|
|
I have the same problem with the blank window, but after I re-emerged from 2.1.4 then upgrade to 2.2.0. The window will resume to normal. It's odded.
_________________
不以物喜, 不以已悲 |
|
| Back to top |
|
|
|
Other Things Gentoo
