went back to vb 5.0.26 and vagrant 1.8.4 issue still remains .... could the corp software be gettiing the way? (jama)
On Monday, August 8, 2016 at 11:29:32 AM UTC+2, Gavin Reid wrote: > > 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) > > > <https://lh3.googleusercontent.com/-6VOntAvinVg/V6hQKKgfVlI/AAAAAAAABwU/BYiyxL0TXB8KorecQPU8giNINPL2ZXdwgCLcB/s1600/2016-08-08_11-17-50.png> > > > > > <https://lh3.googleusercontent.com/-LrkgT3nPPkM/V6hQTDWosqI/AAAAAAAABwY/d1KBQE2UNtsbcofJJw5gzr12Dw3xTZ1_wCLcB/s1600/2016-08-08_11-25-04.png> > > > > > 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 > > On Monday, August 8, 2016 at 11:05:55 AM UTC+2, Gavin Reid wrote: >> >> >> >> $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 >> >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/6a2cc9d9-0db0-47ab-87dd-cb818b2a1eed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
