I get the same with OSX 10.10.1, Vagrant 1.7.1 and VMWare Fusion 7.1.0, while using private_network option.
On Tuesday, 9 September 2014 17:30:13 UTC+1, Ostin Drais wrote: > > Running Vagrant 1.6.5 with vagrant-vmware-fusion 3.0.1 plugin on OS X > 10.9.4. > > I cannot login to a vagrant vm using the "vagrant ssh" command. Doing so > returns the following error: > > "ssh: Could not resolve hostname unknown: nodename nor servname provided, > or not known" > > This tells me the host is not getting a proper name. If I run vagrant > ssh-config, I get the following: > > Host default > > HostName unknown > > User vagrant > > Port 22 > > UserKnownHostsFile /dev/null > > StrictHostKeyChecking no > > PasswordAuthentication no > > IdentityFile [key file path] > > IdentitiesOnly yes > > LogLevel FATAL > > I can ssh into the box manually, i.e. ssh -i [key file path] > [username]@[IP] > I have colleagues with the exact same Vagrantfile configuration on the > same kind of host machine who are not having any issues. > I've attached a scrubbed version of that Vagrantfile config. > > Any thoughts/ideas/questions would be quite helpful. Thanks. > Ostin > > > -- 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]. For more options, visit https://groups.google.com/d/optout.
