cant start up vagrant derived boxes in virtualbox

[Gavin Reid]

$VBoxManage --version

5.1.2r108956

$vagrant --version

Vagrant 1.8.5

Hi ,  Having trouble bringing vagrant derived boxes up , I get the feeling this was working prior to os x 10.11.6 , but its a corp workstation so anything could be fiddling around in the machine (jama).

$vagrant up

Bringing machine 'default' up with 'virtualbox' provider...

==> default: Clearing any previously set forwarded ports...

==> default: Clearing any previously set network interfaces...

==> default: Preparing network interfaces based on configuration...

    default: Adapter 1: nat

==> default: Forwarding ports...

    default: 22 (guest) => 2222 (host) (adapter 1)

==> default: Booting VM...

There was an error while executing `VBoxManage`, a CLI used by Vagrant

for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "b4323fc9-ca18-4879-9bb2-33f6d2c4a469", "--type", "headless"]

Stderr: VBoxManage: error: The VM session was aborted

VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component SessionMachine, interface ISession

in the VB gui , I notice the invalid settings detected icon at the bottom

 box will not start until I open the network and change Adapter 1 from NAT to NAT Network

this is regardless of what box I use , mine or downloaded all fail the same way

removed both virtualbox and vagrant and reinstalled, but still issue remains.

Host OS is OSx 10.11.6

Any ideas what to check next?

Apologies English is not my mother tongue

[Alvaro Miranda Aguilera]

Can you check under networking, that a Nat network with DHCP enable does exist?

--
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 vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/529aac1d-0225-4f03-ae02-11dfd4c87a51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

(+31)103400555

[Gavin Reid]

Hi , after the vagrant up , the config looks like this :

note NAT , not NAT network (i have to manually put it to Nat Network or it will not boot)

its almost like vagrant does not want to use NAT Network.

and there is only one :

VBoxManage natnetwork list

NAT Networks:

Name:        NatNetwork

Network:     10.0.2.0/24

Gateway:     10.0.2.1

IPv6:        No

Enabled:     Yes

1 network found

[Gavin Reid]

went back to vb 5.0.26 and vagrant 1.8.4 issue still remains .... could the corp software be gettiing the way? (jama)

[Gavin Reid]

OK , up until now I have been using wifi only , if i switched to a fixed ethernet connection it just works :(

so now how do i get it to work with wifi .....

[Sean Robbins]

I have this exact same issue. Could not get this to work on vb 5.0.26 or vb 5.1.4

I rolled back to 5.0.16 -  http://download.virtualbox.org/virtualbox/5.0.16/ and the problem goes away (tried this version as a colleague had no problem and this was the version that he had).

Looks like there might be some issue introduced between vb 5.0.16 and 5.0.26 that affects the NAT on OS X 10.11.6

[Gavin Reid]

Hi Sean , try removing all your "locations" in the system preferences

I did this and it helped for a while , however I am in a corp environment and I suspect my network settings are being pushed to the machine with JAMF

--
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 a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/HlmSsVlnaHk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/8dd66c8c-5ed7-40fa-a934-489420004061%40googlegroups.com.