I think it's related to networking. If I remove the private network option from the Vagrantfile, it doesn't happen.
On Wednesday, November 5, 2014 2:56:32 PM UTC-5, Russ Egan wrote: > > I'm running into the same problem, but it doesn't appear to be because of > the multiple CPUs. Happens even with a single vcpu. I'm running with > fusion 7.0.1 on Yosemite, latest vagrant. The ssh config is only messed up > after the initial `up` command. If I shut down the VM and bring it up > again, its resolved. > -- 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.
