It used to help to switch to trusty32, but the situation now got worse again: I tried to use Homestead 2.0 and now I've got the Connection Timeout problem again, which would't usually be a problem, because switching to 32bit helped before. But now I can't just add a line like config.vm.box="ubuntu/trusty32" because we don't have a classic Homestead.yaml file anymore, the values in the new 2.0 Homestead.yaml file just seem to be inserted into the real one in the background and there ist no Vagrantfile available that I could manually edit ...

希望有人能帮忙……

我对这个问题的解决方案是，我的旧笔记本电脑启动时间太长了。我打开虚拟盒子，连接到盒子，等待屏幕加载。花了大约8分钟。

然后它连接并安装了我的文件夹，继续运行。

有时候要有耐心!

我找到的解决方案是检查连接到NAT的适配器1中的电缆连接选项。我真的不知道，这是我的第四个流浪者盒子，但这是唯一一个没有选中电缆连接选项的盒子，检查它后，它工作了。

而不是ctrl-d-ing出虚拟框，因为我习惯做每当我ssh到任何东西，我相信流浪者更喜欢你进入另一个终端，并做一个:

流浪汉瘸腿

让盒子停下来。然后回到VB就没有问题了。

在我的情况下，给它一个静态IP地址，简单地解决了问题:

Config.vm.network "private_network"， ip: "192.168.50.50"

需要反复检查的一件事是，您的计算机BIOS中是否启用了硬件虚拟化。

我的问题是相同的超时字符串，但我只能在GUI中看到黑屏。

我刚刚安装的一台笔记本电脑一直显示同样的问题。经过几个小时的搜索，我终于找到了一个提示，看看BIOS是否启用了硬件虚拟化。

以下是我找到的帖子内容:

我发现仍然有一些用户遇到了这个问题。因此，我将尝试在下面总结一些可能的解决SSH超时问题的方法:

Make sure your firewall or antivirus is not blocking the program (which I doubt will happen often) Give your vagrant machine some time for timeouts to happen. If you dont have a very fast PC / Mac, the VM will take while to boot into an SSH ready state, so timeouts will happen. Therefore, first try to let vagrant timeout COMPLETELY before concluding that there is a fault. If vagrant times out completely then increase the timeout limit in the vagrant file to a few min and try again. If that still doesnt work, then try to clean boot your vagrant machine through the VirtualBox interface and enable the GUI of the machine beforehand. If the GUI doesn't show anything happening (ie. just blackscreen, no text) while it is booting, then your vagrant machine has got problems. Destroy the entire machine through the VB interface and reinstall. Delete the ubuntu image files in the Vagrant Images folder in the user folder and redownload and install. Do you even have an intel processor that supports 64bit hardware virtualisation? Google it. If you do, make sure there is no setting in your Bios disabling this feature. Disable hyper-v feature if you are running windows 7 or 8. Google how to disable. Make sure you are running through an SSH enabled client. Use Git bash. Download: http://git-scm.com/downloads Install a 32bit version of ubuntu like trusty32 or precise32. Just change the version in the vagrant file and reinstall vagrant in new directory. Make sure you are using the latest vagrant and virtualbox versions. Last resorts: Format your computer, reinstall windows and buy an intel core isomething processor.

希望这能有所帮助。