Sylvia

Hi @taru-garg-hashicorp ! Sure, here is the output of `vagrant ssh-config`: ``` Host default HostName 10.211.55.40 User vagrant Port 22 UserKnownHostsFile /dev/null StrictHostKeyChecking no PasswordAuthentication no IdentityFile /Users/user/.vagrant.d/insecure_private_keys/vagrant.key.ed25519 IdentityFile /Users/user/.vagrant.d/insecure_private_keys/vagrant.key.rsa...

Yes, I had also looked into these parts of the logs - it is not so clear to me what "command" the messages refers to. I double-checked, I have both...

I re-installed Parallels like you suggested, but this didn't change the behavior I described. However, meanwhile I noticed/figured out another detail to add to the error description that might get...

Adding here: I also run into exactly the "Host Unreachable" issue when trying to run the vagrant parallels provider via molecule for testing Ansible roles. Probably this is not surprising,...