我有一个Ubuntu13.10,我安装了Vagrant1.5.4和VirtualBox 4.3.10r93012。当我第一次正确地编写虚拟机脚本时,当我编写命令vagrant up时,我的问题就发生了。但是,在执行vagrant halt并再次编写命令vagrant up之后,出现了一个问题:
vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
default: Warning: Connection timeout. Retrying...
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.有什么解决办法吗?谢谢。
发布于 2014-06-15 11:31:39
我增加了使用config.vm.boot_timeout的时间。但对我来说,这并不是原因,尽管错误说明了超时。
我使用vim打开了Vagrantfile,并添加了下面的行,这些行打开了VM的GUI。
config.vm.provider :virtualbox do |vb|
vb.gui = true
end在重新运行vagrant up之后,我在GUI中看到了真正的原因。有一个错误对话框,它一直在等待。这就是连接超时的原因。
为了解决这个问题,我必须在系统BIOS中做一些配置。我必须打开情报VT设置。并请检查AMD-V设置以及.这些设置有助于硬件虚拟化。
发布于 2016-10-06 09:33:54
选择您的Ubuntu服务器,单击“设置”,转到“网络”选项卡,并确保您的电缆连接的选项被选中。

发布于 2014-07-17 09:35:56
我用“流浪汉毁灭”来解决问题。
此命令停止正在运行的机器Vagrant正在管理并销毁在机器创建过程中创建的所有资源。运行此命令后,您的计算机应该处于干净的状态,就好像您从未创建客户机器一样。
https://stackoverflow.com/questions/23293071
复制相似问题