检查CPU在BIOS设置中的虚拟化是否已启用。

将ubuntu32位安装到AMD64位上就成功了。我无法访问BIOs，因为它是一个受限制的环境，但我仍然能够让它与ubuntu/trusty32而不是ubuntu/trusty64一起工作

在Windows 7 SP1上使用Vagrant 1.6.3和VirtualBox 4.3.15

希望这能有所帮助。

有这个问题超过一个星期，尝试了所有的解决方案，

1. giving SSH username and password
2. Enabling GUI interface
3. Updated Virtual Box and Vagrant

毫无效果。

终于从这个环节得到了解决方案

将谷歌公共DNS IP添加到您的Wifi设置中

在Network Preferences下面> Wifi > Advanced > DNS add IP Address 8.8.8.8

完美的工作。也许这可以帮助任何在Mac上有问题的人。 由于Skovmand

SSH连接在初始启动时超时可能与多种原因有关，例如:

check whether virtualization is enabled in BIOS (as per comment), system awaits for user interaction (e.g. share partition is not ready), mismatch of your private key (check the config via vagrant ssh-config), the booting process takes much longer time (try increasing config.vm.boot_timeout), it's booting from the wrong drive (e.g. from the installer ISO), VM firewall misconfiguration (e.g. iptables configuration), local firewall rules, port conflict or conflict with a VPN software, sshd misconfiguration.

要调试问题，请运行——debug选项或如下:

VAGRANT_LOG=debug vagrant up

如果没有什么明显的，那么尝试从另一个终端连接到它，通过vagrant ssh或通过:

vagrant ssh-config > vagrant-ssh; ssh -F vagrant-ssh default

如果SSH仍然失败，尝试使用GUI(例如config. exe)运行它。GUI = true)。

如果不是，检查正在运行的进程(例如:vagrant ssh -c ' pstrree -a')或验证您的sshd_config。

如果它是一次性的虚拟机，你总是可以尝试破坏它，并重新启动它。

你也应该考虑升级你的Vagrant和Virtualbox。

有关详细信息，请检查调试和故障排除页面。

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

希望这能有所帮助。

就像有些人已经指出的那样，如果VirtualBox映像没有正确引导，就会出现错误。对我来说，在《Vagrant》中使用GUI模式并没有太大帮助，因为它只显示一个黑色窗口。在virtualbox GUI中，我检查了虚拟机的设置，发现操作系统设置不正确(Debian 32而不是64位)。

所以我只能建议手动检查虚拟机的VirtualBox设置，让虚拟机启动，而不是首先使用Vagrant。