流浪者卡在连接超时重试中

我的流浪汉昨晚工作得很好。我刚打开电脑，点击《流浪者》，这就是我得到的:

==> 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: 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: Error: Connection timeout. Retrying...
    default: Error: Connection timeout. Retrying...
    default: Error: Connection timeout. Retrying...
    default: Error: Connection timeout. Retrying...
    default: Error: Connection timeout. Retrying...
    default: Error: Connection timeout. Retrying...
    default: Error: Connection timeout. Retrying...
    default: Error: Connection timeout. Retrying...
    default: Error: Connection timeout. Retrying...
    default: Error: Connection timeout. Retrying...
    default: Error: Connection timeout. Retrying...
    default: Error: Connection timeout. Retrying...
    default: Error: Connection timeout. Retrying...

有人吃过这个吗?vagrant在网络上还没有被广泛报道，我也找不到发生这种情况的原因。

当前回答

我是这样做的:

“vagrant up”启动虚拟机后，关闭虚拟机，在虚拟框中进入新的虚拟机设置。然后点击“网络”->“高级” 适配器类型:我从“英特尔PRO XXXXX”改为“PCNet-Fast”(或任何其他适配器除了英特尔PRO确实工作)

2017-04-02 12:12:35

其他回答

我在《Vagrant 1.6.5》和《Virtual Box 4.3.16》中也遇到了同样的问题。在https://github.com/mitchellh/vagrant/issues/4470上描述的解决方案对我来说很好，我只需要删除VirtualBox 4.3.16并安装旧版本4.3.12。

2014-10-08 09:59:01

这是流浪者的新“特征”。看看这里: https://github.com/mitchellh/vagrant/issues/3329

他们将把“错误”改为“警告”。它只是告诉你机器还没有启动，它正在尝试连接…

2014-05-08 19:32:52

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

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

2017-12-10 04:52:58

也许这是一个太简单的答案，以帮助许多人，但值得一试，如果你没有:做一个“流浪者暂停”，而不是“流浪者暂停”，然后重新启动VM与“流浪者up”。

我认为我的问题是由于一些“kworker”进程出现bug，并且在VM中不断超时，所以做硬重启似乎正确地重新加载进程，而保存和恢复只是在其破碎状态下恢复破碎的进程。

2015-04-16 10:08:49

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 ...

希望有人能帮忙……

2014-11-19 05:08:26

流浪者卡在连接超时重试中

推荐文章

最新文章

标签