Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Cannot Start VirtualBox #7212
This morning, the vagrant up command yielded this:
Host operating system
Guest operating system
This is the operating system you run in the virtual machine.
# Copy-paste your Vagrantfile here
Please note, if you are using Homestead or a different Vagrantfile format, we
What should have happened?
What actually happened?
Steps to reproduce
This is what I get when I run that command:
"sudo: /Library/StartupItems/VirtualBox/VirtualBox: command not found"
On Wed, Apr 6, 2016 at 12:54 PM, Seth Vargo firstname.lastname@example.org
There is nothing attached. You cannot send attachments to GitHub. Please follow the instructions on https://www.vagrantup.com/docs/other/debugging.html which explain how to generate debug output to a file. Put the contents of the file into a GitHub Gist and send the link here. Thanks!
I'm completely confused about gists (never created one before). At the Create a New Gist window, I entered a message title, "Error Message When Attempting VVV Startup," then entered a filename (vagrant.log), pasted the content copied from my CLI into the window below the title & filename, and clicked "Create secret gist." The result was an error message saying, "Contents can't be empty."
I'm at a loss. Please advise.
Here's the URL to the gist:
Can you try the following? (You need to find the launch agent on your machine):
Here are a few posts to help:
I tried this:
and got this error message:
I'm able to bring up the Oracle VM VirtualBox Manager, but I then get a prompt for a password within VB & whatever it is, I don't know it (evidently, it's not my logon password, unless I have to preface it with sudo).
Thank you for your reply. Please understand that you cannot attach files to your email replies. If you look on #7212 (where this thread is), you will see that there are no attachments.
As I said above, you need to restart the Virtualbox daemon. This varies between operating systems. Can you please try @DevNaga's suggestion:
sudo /etc/init.d/vboxdrv restart
yields this message:
Stopping VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...failed!
(modprobe vboxnetflt failed. Please use 'dmesg' to find out why)
I'm not sure where to add 'dmesg' to the command to get the info referred to above.
You may need to install the generic headers:
Please note, we are willing to help you debug this issue, but this is no longer a Vagrant issue. The issue you are experiencing is entirely with Virtualbox.
Given that this is a VirtualBox issue, can you point me to anyone over
Here's what I've tried since I got your email above:
I ran this command:
$ dmesg | grep VirtualBox
getting this result:
[ 5067.037574] warning: `VirtualBox' uses 32-bit capabilities (legacy
Then I ran
sudo modprobe -v vboxdrv
which did absolutely nothing after I entered the password at the prompt:
$ sudo modprobe -v vboxdrv
$ sudo apt-get install linux-headers-generic build-essential
got me this:
Reading package lists... Done
Then I tried this:
sudo depmod -a
and then modprobe again:
sudo modprobe -v vboxdrv
which again yielded nothing.
Btw, I really appreciate your help.
On Wed, Apr 6, 2016 at 4:22 PM, Seth Vargo email@example.com wrote:
I'm on a 64-bit machine. I noticed that entry, too & wondered about it
On Wed, Apr 6, 2016 at 5:20 PM, Seth Vargo firstname.lastname@example.org wrote: