对我来说有用的是从BIOS允许64位操作系统(Ubuntu 13.10)上的64位虚拟化。

这里有很多很好的答案，我不能全部读完，但是，我只是来给我的一点贡献。我有两个不同的问题:

vagrant up wasn't able to find my ssh 'id_rsa' (because I didn't have it yet, at that time): I ran ssh-keygen -t rsa -b 4096 -C "myemailaddress@mydomain.com", based on this GitHub's article, and voilá, steped through that; Then, I got the same problem of this question "Warning: Connection timed out. Retrying...", eternally...: So, after reading a lot, I've restarted my system and looked at my BIOS (F2 to get there, on PC), and there were Virtualization disabled. I've enabled that, saved, and started the system once again, to check if it has changed anything.

从那以后，流浪起来就像有魔力一样!现在是凌晨4点，但它还在跑!多酷啊，hã?我知道很少有像我这样的受虐狂开发者会在Windows上尝试这个，特别是在Windows 10上，我只是无法不忘记来这里并留下我的话…另一个重要的信息，是，我试图设置Laravel 5，使用Homestead, VirtualBox，作曲家等。这是有效的。所以，希望这个答案能对你有所帮助，就像这个问题和答案对我有所帮助一样。祝福你。G-bye !

我解决了这个问题，如果其他人有类似的问题，我会回答。

我所做的是:我启用了虚拟框的GUI，让它在启动时等待输入，以选择我是想直接引导到ubuntu还是safemode等等。

要打开GUI，你必须把这个放在你的Vagrantfile配置中:

config.vm.provider :virtualbox do |vb|
  vb.gui = true
end

需要反复检查的一件事是，您的计算机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.

希望这能有所帮助。

删除文件:

C:\Users\UserName\\.vagrant.d\insecure_private_key

然后运行:

vagrant up

我也遇到过同样的问题。我通过在BIOS设置中启用虚拟化来解决这个问题。