The last week I've been having a heck of a time keeping a consistent vm running. It always seems to die when I'm ssh'd in and running things, leave it idle for a time (seems to die faster with the vmware provider than the virtualbox one but happens with both), and always exists with:
packet_write_wait: Connection to 172.16.126.190: Broken pipe And then after that if I do a "vagrant ssh" it sits there and silently exits after trying for a minute or so. In the past 3 days I've probably done "vagrant destroy && vagrant up" about a dozen times or more. It used to work quite reliably. I have Vagrant 1.8.1 installed with VMware Fusion 8.0.1 and VirtualBox 5.0.14. I finally installed VirtualBox just to try it because VMware was ticking me off. I had previously had Fusion 8.1 installed and suffered from the broken port forwarding nonsense. I don't know if I need to trash everything and reinstall (which I did numerous times before when I upgraded to 8.1), or what, but this is driving me batty. Googling doesn't seem to help provide any answers. I'm at my wits end as I'm trying to get some real work done, but I'm spending all my time rebuilding these silly vagrant vms. Any ideas? I'm running on OS X 10.11.3. -- 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/e98512da-1947-4b4b-b4d3-352223bdb1f2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
