2017-01-07 16:53 GMT+02:00 gevisz <[email protected]>: > 2017-01-07 16:32 GMT+02:00 J. Roeleveld <[email protected]>: >> On January 7, 2017 3:06:26 PM GMT+01:00, gevisz <[email protected]> wrote: >>>2017-01-07 15:19 GMT+02:00 Alan McKinnon <[email protected]>: >>>> On 07/01/2017 15:01, gevisz wrote: >>>>> The installed version fails to launch Win7x64 >>>>> with the following messages: >>>>> >>>>> Failed to open a session for the virtual machine Win7x64. >>>>> >>>>> The virtual machine 'Win7x64' has terminated unexpectedly during >>>>> startup with exit code 1 (0x1). >>>>> >>>>> >>>>> Kernel driver not installed (rc=-1908) >>>> >>>> please post lsmod >>> >>># lsmod >>>Module Size Used by >>>kvm_amd 50171 0 >>>kvm 431785 1 kvm_amd >>>irqbypass 2680 1 kvm >>> >>>> Do you have the vbox modules listed in /etc/conf/d/modules to >>>autoload? >>> >>>If you meant /etc/conf.d/modules, it contains the following: >>># Added for VirtualBox: >>>modules="vboxdrv vboxpci vboxnetadp vboxnetflt" >>> >>>> Did you recompile the vbox modules after upgrading vbox for the >>>current >>>> running kernel? >>> >>>Yes, I have recompiled app-emulation/virtualbox-modules-4.3.38 >>>several times today, and it recompiled without errors. >>> >>>>> The VirtualBox Linux kernel driver (vboxdrv) is either not loaded >>>>> or there is a permission problem with /dev/vboxdrv. Please reinstall >>>>> the kernel module by executing >>>>> >>>>> '/etc/init.d/vboxdrv setup' >>>> >>>> this will not work, that file does not exist on Gentoo. >>> >>>Yes, this file does not exists, but I have tried to do what >>>the error message from VirtualBox suggested. >>> >>>> It's probably a hard-coded vbox-ism that does not apply here >>>> >>>> >>>>> >>>>> as root. If it is available in your distribution, you should install >>>>> the DKMS package first. This package keeps track of Linux kernel >>>>> changes and recompiles the vboxdrv kernel module if necessary. >>>>> >>>>> as well. :( >>>>> >>>>> Earlier, that is, before a few updates everything worked well. >>>>> >>>>> # /etc/init.d/vboxdrv setup >>>>> bash: /etc/init.d/vboxdrv: No such file or directory >>>>> >>>>> $ eix dkms >>>> >>>> No man. A simple google search would have told you this is a >>>> Debian/Ubuntu feature and has NOTHING to do with Gentoo. >>> >>>Again, I have just tried to do what the error message from VirtualBox >>>suggested. >>> >>>> It rebuilds modules on debian. The gentoo way is >>>> >>>> emerge @module-rebuild >>> >>>This does not help. >>> >>>> and you should see it build vbox modules >>> >>>Yes, it does rebuild app-emulation/virtualbox-modules-4.3.38 >>>but it does not help. >>> >>>> -- >>>> Alan McKinnon >>>> [email protected] >>>> >>>> >> >> Try manually installing all the modules: >> >> # modprobe <modulename> >> >> The list of modules are in that modules line. >> > > Hm, after executing > # modprobe vboxdrv > # modprobe vboxpci > # modprobe vboxnetadp > # modprobe vboxnetflt > vm Win5x64 starts without problems.
But it fails to rebuild anyway. :(
