Virtualbox module gone after latest update

Stan Schymanski stanislaus.schymanski at env.ethz.ch
Wed Feb 15 22:55:14 CET 2017


Update: I tried `sudo dpkg-reconfigure virtualbox-dkms` but it returned:

Loading new virtualbox-5.1.8 DKMS files...
Building only for 4.9.0-0.bpo.1-amd64
Building initial module for 4.9.0-0.bpo.1-amd64
Error! Bad return status for module build on kernel: 4.9.0-0.bpo.1-amd64 
(x86_64)
Consult /var/lib/dkms/virtualbox/5.1.8/build/make.log for more information.

Is virtualbox-dkms incompatible with the new kernel, perhaps?

Cheers

Stan


On 02/15/2017 10:35 PM, Stan Schymanski wrote:
> Dear Daniel,
>
> Since the latest update (yesterday or Monday I think), I cannot start 
> my virtualbox vms any more. When following the instructions and doing 
> `sudo modprobe vboxdrv`, I get: `modprobe: FATAL: Module vboxdrv not 
> found.`
>
> Do you know a workaround? Thanks for your help!
>
> Cheers
>
> Stan
>
>

-- 
___________________________________________

Dr. Stan Schymanski
ETH Zürich
Department of Environmental Systems Science
Soil and Terrestrial Environmental Physics
IBP-STEP
Universitätstrasse 16
8092 Zürich
Schweiz

Room: CHN E 50.2
Ph: +41 44 633 63 65
___________________________________________



More information about the bfh-linux-users mailing list