Skip to content
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

Closed
anonRegions opened this issue Apr 6, 2016 · 25 comments
Closed

Cannot Start VirtualBox #7212

anonRegions opened this issue Apr 6, 2016 · 25 comments

Comments

@anonRegions
Copy link

@anonRegions anonRegions commented Apr 6, 2016

This morning, the vagrant up command yielded this:

Command: ["hostonlyif", "create"]

Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg*)" at line 71 of file VBoxManageHostonly.cpp

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

  1. vagrant up

References

@sethvargo
Copy link
Contributor

@sethvargo sethvargo commented Apr 6, 2016

Hi @anonRegions

Can you please try running:

sudo /Library/StartupItems/VirtualBox/VirtualBox restart

This is not really a Vagrant issue; something became out of sync in Virtualbox's internal cache. Restarting it usually does the trick. 😄

@anonRegions
Copy link
Author

@anonRegions anonRegions commented Apr 6, 2016

Seth--

This is what I get when I run that command:

"sudo: /Library/StartupItems/VirtualBox/VirtualBox: command not found"

Please advise.

Thanks.

Ethan

beyondtheframe@gmail.com

Ethan Rips
beyondtheframe@gmail.com
https://www.linkedin.com/in/ethanrips

On Wed, Apr 6, 2016 at 12:54 PM, Seth Vargo notifications@github.com
wrote:

Hi @anonRegions https://github.com/anonRegions

Can you please try running:

sudo /Library/StartupItems/VirtualBox/VirtualBox restart

This is not really a Vagrant issue; something became out of sync in
Virtualbox's internal cache. Restarting it usually does the trick. [image:
😄]


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#7212 (comment)

@sethvargo
Copy link
Contributor

@sethvargo sethvargo commented Apr 6, 2016

Hi @anonRegions

Do you have Virtualbox installed? If so, at what version? The debug output you pasted only includes one line of output.

@anonRegions
Copy link
Author

@anonRegions anonRegions commented Apr 6, 2016

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
figure out where they reside.)

@anonRegions
Copy link
Author

@anonRegions anonRegions commented Apr 6, 2016

Here's the VBoxLog

@anonRegions
Copy link
Author

@anonRegions anonRegions commented Apr 6, 2016

The current version of VirtualBox is 5.0.16 r105871.

@sethvargo
Copy link
Contributor

@sethvargo sethvargo commented Apr 6, 2016

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!

@anonRegions
Copy link
Author

@anonRegions anonRegions commented Apr 6, 2016

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.

@anonRegions
Copy link
Author

@anonRegions anonRegions commented Apr 6, 2016

Cancel previous transmission--stupid user error.

@anonRegions
Copy link
Author

@anonRegions anonRegions commented Apr 6, 2016

@sethvargo
Copy link
Contributor

@sethvargo sethvargo commented Apr 6, 2016

Hi @anonRegions

Can you try the following? (You need to find the launch agent on your machine):

sudo /Library/Application\ Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh restart

Here are a few posts to help:

@madmax440
Copy link

@madmax440 madmax440 commented Apr 6, 2016

thats a ubuntu 14.04...

the sudo apt-get install virtualbox would have already gotten the virtualbox setup. If not this error might appear.

Probably pasting the error output of /etc/init.d/vboxdrv setup might be helpful..

@anonRegions
Copy link
Author

@anonRegions anonRegions commented Apr 6, 2016

I tried this:

sudo launchctl load /Library/LaunchDaemons/org.virtualbox.startup.plist

and got this error message:

/Library/Application Support/VirtualBox/LaunchDaemons/VirtualBoxStartup.sh: command not found

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).

@anonRegions
Copy link
Author

@anonRegions anonRegions commented Apr 6, 2016

I'm not sure about the error output, but I copied the contents of vboxdrv & the file is attached.

Please advise.

@sethvargo
Copy link
Contributor

@sethvargo sethvargo commented Apr 6, 2016

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

@anonRegions
Copy link
Author

@anonRegions anonRegions commented Apr 6, 2016

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.

@sethvargo
Copy link
Contributor

@sethvargo sethvargo commented Apr 6, 2016

Hi @anonRegions

You may need to install the generic headers:

sudo apt-get install linux-headers-generic build-essential

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.

Refs: http://ubuntuforums.org/showthread.php?t=1098946

@anonRegions
Copy link
Author

@anonRegions anonRegions commented Apr 6, 2016

Seth--

Given that this is a VirtualBox issue, can you point me to anyone over
there who can help me? Their website doesn't seem to list any kind of
support that I could find.

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
support in use)

Then I ran

sudo modprobe -v vboxdrv

which did absolutely nothing after I entered the password at the prompt:

$ sudo modprobe -v vboxdrv
[sudo] password for selfspunwebs:

Trying this:

$ sudo apt-get install linux-headers-generic build-essential

got me this:

Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version.
linux-headers-generic is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

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

beyondtheframe@gmail.com

Ethan Rips
beyondtheframe@gmail.com
https://www.linkedin.com/in/ethanrips

On Wed, Apr 6, 2016 at 4:22 PM, Seth Vargo notifications@github.com wrote:

Hi @anonRegions https://github.com/anonRegions

You may need to install the generic headers:

sudo apt-get install linux-headers-generic build-essential

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.

Refs: http://ubuntuforums.org/showthread.php?t=1098946


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#7212 (comment)

@sethvargo
Copy link
Contributor

@sethvargo sethvargo commented Apr 6, 2016

Hi @anonRegions

Are you on a 32-bit system or are you trying to run Virtualbox inside another virtualization layer?

https://www.virtualbox.org/wiki/Community

@anonRegions
Copy link
Author

@anonRegions anonRegions commented Apr 6, 2016

I'm on a 64-bit machine. I noticed that entry, too & wondered about it
because I was under the distinct impression that I'd installed the 64-bit
version of VirtualBox. Weird...

beyondtheframe@gmail.com

Ethan Rips
beyondtheframe@gmail.com
https://www.linkedin.com/in/ethanrips

On Wed, Apr 6, 2016 at 5:20 PM, Seth Vargo notifications@github.com wrote:

Hi @anonRegions https://github.com/anonRegions

Are you on a 32-bit system or are you trying to run Virtualbox inside
another virtualization layer?

https://www.virtualbox.org/wiki/Community


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#7212 (comment)

@sethvargo
Copy link
Contributor

@sethvargo sethvargo commented Apr 6, 2016

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!

@sethvargo sethvargo closed this Apr 6, 2016
@anonRegions
Copy link
Author

@anonRegions anonRegions commented Apr 6, 2016

Thank you, Seth!

@kelvinkyaw
Copy link

@kelvinkyaw kelvinkyaw commented Sep 26, 2018

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.

@ederrafo
Copy link

@ederrafo ederrafo commented Jul 21, 2019

In macOS Mojave, simple update virtualbox , if use vagrant also update it, your vm not will suffer change

@ghost
Copy link

@ghost ghost commented Jan 28, 2020

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.

@hashicorp hashicorp locked and limited conversation to collaborators Jan 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants