Just came across this on Google; thought I would share my findings: The vm.gui option did indeed open a dialog asking if I wanted to "upgrade" my VM. I chose "Never ask me again". The problem still existed.
I recently upgraded from Fusion 5, to Fusion 6, so I thought it might be a compat problem. Reinstalling Fusion 5 overwrote 6 - so I renamed that to "Fusion 5" and then reinstalled 6 alongside it. Then things starting working again... Which would imply that a reinstall of VMWare Fusion 6 is sufficient to fix this :/ On Wednesday, 12 February 2014 06:03:47 UTC+11, Alvaro Miranda Aguilera wrote: > > what the guest os? > > can you share a gist with > > vagrantfile > ifconfig -a > cat /etc/sysconfig/network-scripts/ifcfg-eth* > > Alvaro. > > > On Wed, Feb 12, 2014 at 1:33 AM, Hongli Lai <[email protected] > <javascript:>> wrote: > >> 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] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- 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.
