-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot Start VirtualBox #7212
Comments
Hi @anonRegions Can you please try running:
This is not really a Vagrant issue; something became out of sync in Virtualbox's internal cache. Restarting it usually does the trick. 😄 |
Seth-- This is what I get when I run that command: "sudo: /Library/StartupItems/VirtualBox/VirtualBox: command not found" Please advise. Thanks. Ethan Ethan Rips On Wed, Apr 6, 2016 at 12:54 PM, Seth Vargo notifications@github.com
|
Hi @anonRegions Do you have Virtualbox installed? If so, at what version? The debug output you pasted only includes one line of output. |
Attached is a file containing the logging info from my terminal, which should give you the information you seek. (I don't know where the VirtualBox error logs are stored. I can send them to you if you help me |
Here's the VBoxLog |
The current version of VirtualBox is 5.0.16 r105871. |
Hi @anonRegions 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. |
Cancel previous transmission--stupid user error. |
Here's the URL to the gist: https://gist.github.com/anonRegions/e02a31fa0a4834904d87d96f33849c80 |
Hi @anonRegions Can you try the following? (You need to find the launch agent on your machine):
Here are a few posts to help: |
thats a ubuntu 14.04... the Probably pasting the error output of |
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). |
I'm not sure about the error output, but I copied the contents of vboxdrv & the file is attached. Please advise. |
Hi @anonRegions 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. |
Hi @anonRegions 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. |
Seth-- 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 Trying this: $ 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. Please advise. Btw, I really appreciate your help. Thanks! Ethan Ethan Rips On Wed, Apr 6, 2016 at 4:22 PM, Seth Vargo notifications@github.com wrote:
|
Hi @anonRegions Are you on a 32-bit system or are you trying to run Virtualbox inside another virtualization layer? |
I'm on a 64-bit machine. I noticed that entry, too & wondered about it Ethan Rips On Wed, Apr 6, 2016 at 5:20 PM, Seth Vargo notifications@github.com wrote:
|
Hi @anonRegions As this is not a Vagrant issue, I'm going to close this. I posted a link to the VirtualBox resources above. Thanks! |
Thank you, Seth! |
Same experience with iOS 12 with VB 5.2.6. Remove old VB version and download new version of VB (5.2.18). Work perfectly. |
In macOS Mojave, simple update virtualbox , if use vagrant also update it, your vm not will suffer change |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
This morning, the vagrant up command yielded this:
Vagrant version
Vagrant 1.7.4
Host operating system
Ubuntu 14.04
Guest operating system
This is the operating system you run in the virtual machine.
Vagrantfile
# Copy-paste your Vagrantfile here
Please note, if you are using Homestead or a different Vagrantfile format, we
may be unable to assist with your issue. Try to reproduce the issue using a
vanilla Vagrantfile first.
Debug output
https://gist.github.com/anonRegions/21f5d6ef141252f986c3054e25ddc87e
Expected behavior
What should have happened?
Actual behavior
What actually happened?
Steps to reproduce
References
The text was updated successfully, but these errors were encountered: