This bug appears to have been fixed in trusty. As I originally said, the
fix is to make sure virtualbox-dkms is installed; the extra command
which I did not give was to run modprobe vboxdrv (though running
/etc/init.d/virtualbox start should also work). (Running
/etc/init.d/virtualbox does not fix
The command /etc/init.d/vboxdrv is in fact missing; however the command
/etc/init.d/virtualbox is present and if run as suggested does make
VirtualBox run correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't have the original build log (you can see I filed the bug seven
months ago). But in any case, the build was successful. I'm not sure how
much clearer I can be about this: there was no problem building the
modules.
The problem was with the command suggested by the system to build the
The original report by you does not give any information about why
/etc/init.d/vboxdrv is missing. That might give a good clue about the
cause of this error. Is it possible for you to remove and reinstall
virtualbox to reproduce the error?
--
You received this bug notification because you are a
The file /etc/init.d/vboxdrv is not missing: it does not exist in
Ubuntu:
http://packages.ubuntu.com/search?searchon=contentskeywords=%2Fetc%2Finit.d%2Fvboxdrvmode=filenamesuite=quantalarch=any
The point is simply that the command is wrong. I'm not sure how I can
make this any clearer. There is
Is this issue fixed by installing linux-headers-lowlatency? If not,
please reopen this bug. Thanks!
** Changed in: virtualbox (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This issue is not fixed by installing linux-headers-lowlatency. Indeed,
I already had it installed.
I seem to have been unclear in my original report: I have no problem
actually building the modules. The problem is that the command given to
build the modules does not work. Instead, I used a
Is it possible for you to post the original build log? The install
process should have built the kernel module and you should not have seen
this error. If the install process did not succeed, the module will be
missing and can cause such error. It would be helpful if you could try
and reproduce
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: virtualbox (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972693
Title:
When using a lowlatency kernel, you have to install the package : linux-
headers-lowlatency
i'm not an expert but it seems that the virtualbox dkms module needs
kernel headers
restart virtualbox with the command : /etc/init.d/virtualbox restart
and start your VM. No need to completely reboot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972693
Title:
Error message for missing kernel modules gives wrong command
To manage notifications about this bug go to:
11 matches
Mail list logo
