I've tried deleting all leases files in /var/db/vmware. I then stopped VMWare Fusion, and re-ran 'vagrant up'. It didn't work this time either. The VM boots properly, but all leases files are empty.
On Tuesday, February 11, 2014 1:27:13 PM UTC+1, Hongli Lai wrote: > > I have Vagrant 1.4.3, VMWare Fusion plugin 2.3.0, VMWare Fusion 6, OS X > 10.9.1. When running 'vagrant up', Vagrant sometimes waits forever for the > VM to boot, even though it's actually up. I cannot always reproduce this > problem: sometimes it works, and sometimes it doesn't work. When it > doesn't, I have to reboot multiple times or it will continue to not work. > > When it doesn't work, the debug logs are as follows: > https://gist.github.com/FooBarWidget/8933808. As you can see, it's > waiting forever because of Vagrant::Errors::SSHNotReady errors. For some > reason, the VMWare DHCP leases file does not include the VM's IP address. > I've posted my /var/db/vmware/vmnet-dhcpd-vmnet8.leases here: > https://gist.github.com/FooBarWidget/8933860. The Vagrant VM's MAC > address is supposed to be 00:0C:29:0D:BD:67. > > My Vagrant VM is started with a GUI, so I confirm that the VM boots > properly and that it gets a network connection properly. 'vagrant status' > also says that the VM is running. > > Why does this problem occur? What can I do to fix it? > -- 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/groups/opt_out.
