I've been hitting the same issue. Here's what I found:

When you clone a VMWare Fusion VM, the network adapter gets a new MAC 
address. However, the contents of /etc/sysconfig/network-scripts/ifcfg-eth0in 
the CentOS VM still have the 
*original* MAC address from when I was building up the box. When I manually 
updated the HWADDR value in that file, vagrant up worked as expected.

You can see a VMWare KB article on this topic here: 
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2002767

Mitchell directed me to this mailing list and suggested that the problem 
can be solved either in the guest VM or the box definition, but did not 
offer specific examples.

Is anyone else familiar with this issue? Is it possible to configure the 
VMWare VM or CentOS in such a way that this does not happen?

Thanks,
Harrison

On Thursday, April 24, 2014 8:15:30 AM UTC-4, Bryan Hughes wrote:
>
> I have a CentOS 5.x VM running on VMWare Fusion 6.0.3. After enabling 
> v.gui=true, I can see that the VM boots, however, Vagrant 1.5.4 seems to be 
> hanging at the "Waiting for the VM to finish booting..." step.
>
> Here's the error that I keep seeing in the debug:
>
>  INFO ssh: SSH not up: #<Vagrant::Errors::SSHNotReady: The provider for this 
> Vagrant-managed machine is reporting that it is not yet ready for SSH. 
> Depending on your provider this can carry
> different meanings. Make sure your machine is created and running and
> try again. Additionally, check the output of `vagrant status` to verify
> that the machine is in the state that you expect. If you continue to
> get this error message, please view the documentation for the provider
> you're using.>
>
> I'm new to Vagrant, so I'm uncertain if I've unwittingly created an issue 
> or if Vagrant is encountering a problem. Any help is appreciated.
>

-- 
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.

Reply via email to