The VM does boot up from the manager.
1. Bring the VM up while not on the VPN, then vagrant halt. 2. Log back into VPN, try to vagrant up and get the usual error. 3. Go to the VMware Virtual Machine library and right click on the shutdown machine and choose Start Up, it comes up. This leads me to think the problem is in the vagrant provider. On Wednesday, December 30, 2015 at 12:26:32 AM UTC-5, Alvaro Miranda Aguilera wrote: > > Hello, > > My impression here will be if you stop that vagrant box, and turn it on > from the VMWare GUI, vmware should give you the same message. If this is > correct, then it looks more as a VMWare feature. > > On the other hand, if vmware boot ok, and vagrant fail, then that will > require more review and seems something more into the vagrant side of > things. > > Any chance you can do that test? > > At any point you can contact support at hashicorp.com for Vagrant + > Vmware integration question/issues too. > > As for VPN, I personally have a VM where I run the vpn software plenty of > issues with different clients, etc. > I can understand is not a valid suggestion for your case, just sharing my > personal opinion on vpn. > > Thanks > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/784765f0-0d81-4a19-a969-3ed516099a25%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
