| 1 |
On 07/01/2017 15:01, gevisz wrote: |
| 2 |
> The installed version fails to launch Win7x64 |
| 3 |
> with the following messages: |
| 4 |
> |
| 5 |
> Failed to open a session for the virtual machine Win7x64. |
| 6 |
> |
| 7 |
> The virtual machine 'Win7x64' has terminated unexpectedly during |
| 8 |
> startup with exit code 1 (0x1). |
| 9 |
> |
| 10 |
> |
| 11 |
> Kernel driver not installed (rc=-1908) |
| 12 |
|
| 13 |
please post lsmod |
| 14 |
|
| 15 |
Do you have the vbox modules listed in /etc/conf/d/modules to autoload? |
| 16 |
Did you recompile the vbox modules after upgrading vbox for the current |
| 17 |
running kernel? |
| 18 |
|
| 19 |
> |
| 20 |
> The VirtualBox Linux kernel driver (vboxdrv) is either not loaded |
| 21 |
> or there is a permission problem with /dev/vboxdrv. Please reinstall |
| 22 |
> the kernel module by executing |
| 23 |
> |
| 24 |
> '/etc/init.d/vboxdrv setup' |
| 25 |
|
| 26 |
this will not work, that file does not exist on Gentoo. |
| 27 |
It's probably a hard-coded vbox-ism that does not apply here |
| 28 |
|
| 29 |
|
| 30 |
> |
| 31 |
> as root. If it is available in your distribution, you should install |
| 32 |
> the DKMS package first. This package keeps track of Linux kernel |
| 33 |
> changes and recompiles the vboxdrv kernel module if necessary. |
| 34 |
> |
| 35 |
> as well. :( |
| 36 |
> |
| 37 |
> Earlier, that is, before a few updates everything worked well. |
| 38 |
> |
| 39 |
> # /etc/init.d/vboxdrv setup |
| 40 |
> bash: /etc/init.d/vboxdrv: No such file or directory |
| 41 |
> |
| 42 |
> $ eix dkms |
| 43 |
|
| 44 |
No man. A simple google search would have told you this is a |
| 45 |
Debian/Ubuntu feature and has NOTHING to do with Gentoo. |
| 46 |
|
| 47 |
It rebuilds modules on debian. The gentoo way is |
| 48 |
|
| 49 |
emerge @module-rebuild |
| 50 |
|
| 51 |
and you should see it build vbox modules |
| 52 |
|
| 53 |
|
| 54 |
-- |
| 55 |
Alan McKinnon |
| 56 |
alan.mckinnon@×××××.com |
Archives