Vagrant connection "bug"

[Mark]

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

[Mark]

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.

[dragon788]

As you mentioned hgfs is the shared folder driver for VMware. Have you updated the open-vm-tools package in your VM or VMware Tools recently?

There are a lot of new security changes in macOS 10.15 so depending on how recent your VMware version is that could be contributing, but try disabling the shared folder and see if it boots properly without failing.