*** This bug is a duplicate of bug 1466046 ***
https://bugs.launchpad.net/bugs/1466046
I also had the secure boot issue after upgrading to Xenial 16.04 LTS.
Rafael's solution was the only one listed that fixed the issue for me.
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1466046 ***
https://bugs.launchpad.net/bugs/1466046
+1 Updated to 16.04, it asked for secure boot, exact same issue.
Disabled secure boot in BIOS, problem went away.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1466046 ***
https://bugs.launchpad.net/bugs/1466046
Guys,
I was in that trouble after upgrading to Xenial. Before vbox and vagrant
worked well on my notebook. While upgrading I saw that secure boot was
re-enabled (I do not remember enabling it). I followed
*** This bug is a duplicate of bug 1466046 ***
https://bugs.launchpad.net/bugs/1466046
please look at bug 1466046 which has a workaround for this bug
** This bug has been marked a duplicate of bug 1466046
virutalbox doesnt run VMs since the vboxdrv module is not loaded
automatically
--
I had a similar issue with Ubuntu v.15.04, and the suggestion to delete
/etc/init.d/vboxdrv worked. For good measure, I deleted all of the
leftover vbox* binaries that were left in /etc/init.d, e.g.:
@billyJr:~$ ls /etc/init.d/vbox*
/etc/init.d/vboxautostart-service/etc/init.d/vboxdrv
Thanks, I'll leave it open for 60 days if somebody has the same problem
** Changed in: virtualbox (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452827
I have reinstalled 14.04 on this machine and VirtualBox is now working.
I won't be able to provide any more information on this issue since:
a) it's working
b) I'm using a different version.
You can close it if you want.
--
You received this bug notification because you are a member of Ubuntu
I don't really know then... Something should have been broken, and
upgrading doesn't seem to fix it... Probably a clean install might do
the trick, but at this point I'm not sure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am experiencing the same problem after upgrading to Vivid from Trusty.
sudo apt-get install virtualbox -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
virtualbox-dkms virtualbox-qt
Suggested
I think the problem is a leftover /etc/init.d/vboxdrv either from a
previous virtualbox install, removing that fixes it for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452827
Title:
The
@mpchlets, I don't have an /etc/init.d/vboxdrv. Did you reinstall
virtualbox after removing that file? Or did just removing it allow
virtualbox to run successfully?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have upgraded to vivid and it has the same problem. Log attached.
** Attachment added: vivid.log
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1452827/+attachment/4395597/+files/vivid.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm really lost, I never had such a problem, and I don't know why you
seem to be the only one experiencing it.
Maybe installing first virtualbox-dkms and later virtualbox might fix
the issue, but I'm really not sure (and not confident)
Anyway, this ubuntu release will be EOL in ~2 months, so it
the module is provided by virtualbox-dkms, but now seems that (since
vivid) the kernel has the driver embedded (it just needs to be built
when vbox is installed).
the /etc/init.d/vboxdrv should be provided by the official package, not
by the Ubuntu one. (it is called etc/init.d/virtualbox
I can't test utopic, please purge vbox and post here the install log
like I did, with the /var/lib/dkms/ build log.
I suspect you installed the official virtualbox and you didn't purge it
correctly somewhere.
** Changed in: virtualbox (Ubuntu)
Status: New = Incomplete
--
You received
please also run apport-collect 1452827
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452827
Title:
The character device /dev/vboxdrv does not exist.
To manage notifications about this bug go to:
apport information
** Tags added: apport-collected utopic
** Description changed:
There was a recent update to Virtualbox that I installed 2 days ago.
See:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1435113/comments/17.
Now, Virtualbox won't start any VMs.
Here's the log of the clean install.
$ sudo apt-get purge dkms virtualbox-dkms virtualbox-qt virtualbox
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
dkms* virtualbox* virtualbox-dkms* virtualbox-qt*
0
Done.
I thought I had linux-headers-generic already installed but apparently I
didn't. Regardless, I still have the same issue. Neither
`/dev/vboxdrv` nor `/etc/init.d/vboxdrv` exist.
** Changed in: virtualbox (Ubuntu)
Status: Incomplete = New
--
You received this bug notification
What package is supposed to provide the `vboxdrv` kernel module? I
don't see anything like that under /lib/modules.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452827
Title:
The character
can you please install linux-headers-generic, and after
sudo apt-get purge virtualbox virtualbox-dkms (and so on)
and sudo apt-get install virtualbox and the other packages?
** Changed in: virtualbox (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are
21 matches
Mail list logo
