Vagrant up 并重新加载 - 默认值：警告：连接超时。正在重试...
Vagrant up and reload - default: Warning: Connection timeout. Retrying...
我有一个功能齐全的流浪者已经三个月了，但是在过去的三天里，每当我尝试 运行 vagrant up 或 vagrant reload 时我都会遇到错误。
这是我在 运行ning vagrant reload
时得到的错误
default: Attempting graceful shutdown of VM...
default: Guest communication could not be established! This is usually because
default: SSH is not running, the authentication information was changed,
default: or some other networking issue. Vagrant will force halt, if
default: capable.
default: Forcing shutdown of VM...
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: 80 => 8080 (adapter 1)
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.
我正在使用 Elementary OS Luna 并根据建议的一些答案更新了最新版本的 vagrant 和 virtualbox。但问题依然存在。
我已经尝试了大多数流行的解决方案，包括启用 GUI 和 this. I also tried the solution given here，但无法成功，因为我的虚拟盒子无法登录。
但是，GUI 向我展示了这个：
keys: press S to skip mounting or M for manual recovery
两个键都一一试过，问题依旧。
有没有人遇到过这个谁可以提供解决方案，vagrant 在网络上还没有被广泛覆盖，我找不到发生这种情况的原因。
在尝试了针对不同问题的所有可用选项之后，我仍然面临着同样的问题。
最后，我做了一个
vagrant destroy
其次是
vagrant up
而且我的系统又可以工作了。
注意：如果你也有直接关机的习惯，你可能很快就会遇到这个问题！在你的 vagrant 终端（vagrant ssh），总是去寻找：
sudo shutdown -h now
或者您可以直接输入
vagrant halt
从 ssh 注销后。
PS：对于那些可能害怕在 vagrant destroy 期间失去 data/code/anything 的人，您可以放松一下！我对使用该命令犹豫不决，但根据文档，它所做的只是：
This command stops the running machine Vagrant is managing and destroys all resources that were created during the machine creation process. After running this command, your computer should be left at a clean state, as if you never created the guest machine in the first place.
这意味着您的代码将保持不变，下一个 vagrant up 会将您带到与离开时相同的状态，只是现在问题已解决。 :)
而不是破坏图像。我能够通过首先在 Vagrantfile 中添加以下 lines/uncomment 来打开 virtualbox gui 来解决这个问题。
config.vm.provider "virtualbox" do |vb|
vb.gui = true
vb.memory = "1024"
end
然后我做了 vagrant up 来重启它。它启动了命令行和 virtualbox gui。 Gui 要求我提供 SSH 密码（这是我上次登录机器时在玩 ssh 时设置的），我能够登录。后来我关闭了图像。后来我从 Vagrantfile 中删除了上面的 gui 行，它仍然可以正常启动。
我有一个功能齐全的流浪者已经三个月了，但是在过去的三天里，每当我尝试 运行 vagrant up 或 vagrant reload 时我都会遇到错误。
这是我在 运行ning vagrant reload
default: Attempting graceful shutdown of VM... default: Guest communication could not be established! This is usually because default: SSH is not running, the authentication information was changed, default: or some other networking issue. Vagrant will force halt, if default: capable. default: Forcing shutdown of VM... 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: 80 => 8080 (adapter 1) 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.
我正在使用 Elementary OS Luna 并根据建议的一些答案更新了最新版本的 vagrant 和 virtualbox。但问题依然存在。
我已经尝试了大多数流行的解决方案，包括启用 GUI 和 this. I also tried the solution given here，但无法成功，因为我的虚拟盒子无法登录。
但是，GUI 向我展示了这个：
keys: press S to skip mounting or M for manual recovery
两个键都一一试过，问题依旧。
有没有人遇到过这个谁可以提供解决方案，vagrant 在网络上还没有被广泛覆盖，我找不到发生这种情况的原因。
在尝试了针对不同问题的所有可用选项之后，我仍然面临着同样的问题。 最后，我做了一个
vagrant destroy
其次是
vagrant up
而且我的系统又可以工作了。
注意：如果你也有直接关机的习惯，你可能很快就会遇到这个问题！在你的 vagrant 终端（vagrant ssh），总是去寻找：
sudo shutdown -h now
或者您可以直接输入
vagrant halt
从 ssh 注销后。
PS：对于那些可能害怕在 vagrant destroy 期间失去 data/code/anything 的人，您可以放松一下！我对使用该命令犹豫不决，但根据文档，它所做的只是：
This command stops the running machine Vagrant is managing and destroys all resources that were created during the machine creation process. After running this command, your computer should be left at a clean state, as if you never created the guest machine in the first place.
这意味着您的代码将保持不变，下一个 vagrant up 会将您带到与离开时相同的状态，只是现在问题已解决。 :)
而不是破坏图像。我能够通过首先在 Vagrantfile 中添加以下 lines/uncomment 来打开 virtualbox gui 来解决这个问题。
config.vm.provider "virtualbox" do |vb|
vb.gui = true
vb.memory = "1024"
end
然后我做了 vagrant up 来重启它。它启动了命令行和 virtualbox gui。 Gui 要求我提供 SSH 密码（这是我上次登录机器时在玩 ssh 时设置的），我能够登录。后来我关闭了图像。后来我从 Vagrantfile 中删除了上面的 gui 行，它仍然可以正常启动。