流浪汉2.0永远不SSH'；把它放进盒子里

因此，我试图通过运行

vagrant init hashicorp/precise64

那当然跑了

vagrant up 

然后，一旦流浪者文件被放置，我运行

vagrant ssh 

然后它超时了，我想知道“流浪者”是否有某种冗长的模式，但这就是我从“流浪者”本身所能得到的

monta@users-MacBook-Pro:~$ vagrant up
Bringing machine 'default' up with 'vmware_fusion' provider...
==> default: Checking if box 'hashicorp/precise64' is up to date...
==> default: Verifying vmnet devices are healthy...
==> default: Preparing network adapters...
WARNING: The VMX file for this box contains a setting that is automatically overwritten by Vagrant
WARNING: when started. Vagrant will stop overwriting this setting in an upcoming release which may
WARNING: prevent proper networking setup. Below is the detected VMX setting:
WARNING:
WARNING:   ethernet0.pcislotnumber = "32"
WARNING:
WARNING: If networking fails to properly configure, it may require this VMX setting. It can be manually
WARNING: applied via the Vagrantfile:
WARNING:
WARNING:   Vagrant.configure(2) do |config|
WARNING:     config.vm.provider :vmare_fusion do |vmware|
WARNING:       vmware.vmx["ethernet0.pcislotnumber"] = "32"
WARNING:     end
WARNING:   end
WARNING:
WARNING: For more information: https://www.vagrantup.com/docs/vmware/boxes.html#vmx-whitelisting
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Starting the VMware VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 172.16.117.136:22
    default: SSH username: vagrant
    default: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

每次都是这样。我使用的是VMWare Fusion provider，这是一个额外的插件，需要额外的费用。我已经在Vagrant文件中指定了这一点

---

如有任何想法、想法、建议，将不胜感激。谢谢你们

hashicorp/precise64确实是最古老的盒子之一，在很多关于流浪但不准确的图坦卡蒙的书中都提到过，你能试试ubuntu/trusty64作为替代品吗？这不是问题所在。我也有同样的错误，但是谢谢弗雷德里克的建议。我认为问题出在Vagrant文件中。我在Vagrant 2.0.0和1.9.8中有相同的问题，但在1.9.6中没有。