Vagrant forever waiting for VMWare Fusion 6 machine to boot

[Hongli Lai]

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?

[Hongli Lai]

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.

[Will Froning]

Hello Hongli,

Have you tried adding vm.gui = true?

I often have issues with boxes that were created with an older version
of Workstation/Fusion, and upon startup Fusion asks you if you'd like to
upgrade the hardware config to the current version. This stops the
system from booting at all until your respond to the alert box.

I haven't found a good solution for this except to create a new box,
maybe someone else has a better solution.

Thanks,
Will

> --
> 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 vagrant-up+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.


--
Will Froning
Will.F...@GMail.com

[Hongli Lai]

On Tue, Feb 11, 2014 at 5:34 PM, Will Froning <will.f...@gmail.com> wrote:
> Hello Hongli,
>
> Have you tried adding vm.gui = true?

Is it already running with vm.gui = true. I confirm in the GUI that
the VM boots properly and has a network connection.

--
Phusion | Ruby & Rails deployment, scaling and tuning solutions

Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)

[Alvaro Miranda Aguilera]

what the guest os?

can you share a gist with

vagrantfile

ifconfig -a

cat /etc/sysconfig/network-scripts/ifcfg-eth*

Alvaro.

--

[Matt Black]

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 :/

[Hongli Lai]

I don't think it has got anything to do with reinstalling. The problem
seems to occur randomly; it disappeared after I rebooted a few times
and waited a day. Sometimes it comes back, only to disappear again
after mysterious conditions. I haven't figured out what triggers the
issue and what mitigates it.

> You received this message because you are subscribed to a topic in the
> Google Groups "Vagrant" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/vagrant-up/dXDH9uDVK9I/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> vagrant-up+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
Phusion | Web Application deployment, scaling, and monitoring solutions