running vagrant up with --debug gives a little more detail (slightly different error?):
*ERROR vagrant: Vagrant experienced an error! Details:* *ERROR vagrant: #<Vagrant::Errors::NetSSHException: An error occurred in the underlying SSH library that Vagrant uses.* *The error message is shown below. In many cases, errors from this* *library are caused by ssh-agent issues. Try disabling your SSH* *agent or removing some keys and try again.* *If the problem persists, please report a bug to the net-ssh project.* *timeout during server version negotiating>* *ERROR vagrant: An error occurred in the underlying SSH library that Vagrant uses.* *The error message is shown below. In many cases, errors from this* *library are caused by ssh-agent issues. Try disabling your SSH* *agent or removing some keys and try again.* *If the problem persists, please report a bug to the net-ssh project.* *timeout during server version negotiating* Has there been a change to OSX / ssh that won't play with vagrant ? Seems unlikely because I can ssh to the VM from terminal with no problem. Vagrant is also connecting to the VM with a username and password, not a stored key. My config has been working fine for years. On Friday, April 17, 2020 at 4:02:50 PM UTC+8, Mark wrote: > > I am seeing a lot of this suddenly: > > > "*Guest-specific operations were attempted on a machine that is not* > > *ready for guest communication. This should not happen and a bug* > > *should be reported.*" > > > which sometimes happens at this point: > > *Waiting for HGFS to become available...* > > > but also sometimes when: > > *Configuring network adapters within the VM...* > > > the box actually boots Ok but vagrant craps out before it does any > provisioning because it cannot connect. I can get to the vm via standard > ssh. > > > nothing in my Vagrantfile has changed for months. I've destroyed and > re-created my vm(s) starting from an empty and a vagrant init. no dice. > totally stuck for ideas. the only thing that has changed recently is that I > now use a wired ethernet adaptor rather than wifi on my macbook (but > reverting to wifi does not correct the problem) > > > I have not upgraded VMWare or Vagrant lately, but probably OSX did update > itself recently to 10.15.4 > > > Obviously I can't get a lot of work done while this is borked so I would > really appreciate some help ASAP, > > cheers > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/74d67130-4b94-4c0f-96f0-6bc8c04fd636%40googlegroups.com.
