NS_ERROR_FAILURE issue on MacOS High Sierra

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

NS_ERROR_FAILURE issue on MacOS High Sierra

Ryan Langley
Hi Everyone,

I'm having a strange issue with Vagrant + VBox on MacOS High Sierra.  I've created a custom Vagrant box for my team, and it works fine on Win10 and MacOS Sierra hosts.  However, one of my team members is on a newer Mac Pro laptop with MacOs High Sierra, and we get the following error when doing the same setup as the other hosts after "vagrant up":

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "a3c41dcb-841b-4395-9a04-28c50eea6781", "--type", "headless"]

Stderr: VBoxManage: error: The virtual machine 'Vagrant_default_1513972955067_49566' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

This error gives very little to go on.  I've researched it for a few days via Google, and have tried multiple suggested fixes like vboxdrv setup, setting DISPLAY env var, verifying host-only network settings, removing and reinstalling vagrant and virtual box, removing ~/.vagrant.d and .vagrant, etc.  Everything gives the same error as above.  It does not even get to a point where it will create a vbox log file.

One small glimmer of the issue is if I manually run:

$ VBoxHeadless -s "vagrant_default"

The VBox VM starts up as expected, however if I manually run:

$ VBoxManage startvm "vagrant_default" --type headless

The VBox VM fails to start with the same error as above.  Has anyone seen this issue before?  Is there a way to force vagrant to use VBoxHeadless instead of VBoxManage?

Vagrant Version: 2.0.1
VirtualBox Version: 5.2.4

Any thoughts would be appreciated, I'm not sure what else to do at this point!

Thanks,
 - Ryan Langley

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/6c664f00-2cd1-49d5-a7ea-42c424a7367e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: NS_ERROR_FAILURE issue on MacOS High Sierra

Alvaro Miranda Aguilera
it seems not a vagrant issue

virtualbox forums like this:

blame things like external drivers no properly removed, or mac os upgrade after virtualbox isntalls (?) and people try reboots / reinstalls

have the virtualbox removed and reinstalled here ?

alvaro

On Tue, Jan 2, 2018 at 11:20 PM, Ryan Langley <[hidden email]> wrote:
Hi Everyone,

I'm having a strange issue with Vagrant + VBox on MacOS High Sierra.  I've created a custom Vagrant box for my team, and it works fine on Win10 and MacOS Sierra hosts.  However, one of my team members is on a newer Mac Pro laptop with MacOs High Sierra, and we get the following error when doing the same setup as the other hosts after "vagrant up":

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "a3c41dcb-841b-4395-9a04-28c50eea6781", "--type", "headless"]

Stderr: VBoxManage: error: The virtual machine 'Vagrant_default_1513972955067_49566' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine

This error gives very little to go on.  I've researched it for a few days via Google, and have tried multiple suggested fixes like vboxdrv setup, setting DISPLAY env var, verifying host-only network settings, removing and reinstalling vagrant and virtual box, removing ~/.vagrant.d and .vagrant, etc.  Everything gives the same error as above.  It does not even get to a point where it will create a vbox log file.

One small glimmer of the issue is if I manually run:

$ VBoxHeadless -s "vagrant_default"

The VBox VM starts up as expected, however if I manually run:

$ VBoxManage startvm "vagrant_default" --type headless

The VBox VM fails to start with the same error as above.  Has anyone seen this issue before?  Is there a way to force vagrant to use VBoxHeadless instead of VBoxManage?

Vagrant Version: 2.0.1
VirtualBox Version: 5.2.4

Any thoughts would be appreciated, I'm not sure what else to do at this point!

Thanks,
 - Ryan Langley

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/6c664f00-2cd1-49d5-a7ea-42c424a7367e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0exsAjW3qRVF%2BJh8YVfoSF1MDJHx2Ay-3wrvWWMNRx5Lrg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: NS_ERROR_FAILURE issue on MacOS High Sierra

Ryan Langley
Thanks for your thoughts Alvaro.

I agree that it does appear to be an issue with the Virtual Box install.  I will check the forum you posted to see if I can make progress, as well as have the team member completely remove VBox, reboot, and then re-install it.

My main motive for posting here was to see if there was a way I could configure Vagrant to use VBoxHeadless rather than VBoxManage.  It seems most likely not, but perhaps it'd be useful in some cases.


--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/07052a67-0d99-4f7a-9f10-6a77def9998a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.