时间戳

首页 > 解决方案 > 当 HyperV 开启时，Vagrant 冻结 SSH 连接

docker - 当 HyperV 开启时，Vagrant 冻结 SSH 连接

问题描述

这是我的配置：

我读到上层配置应该可以在不切换“hypervisorlaunchtype”的情况下工作，但是出了点问题：

λ vagrant up                                                                       
Bringing machine 'default' up with 'virtualbox' provider...                        
==> default: Checking if box 'sternpunkt/jimmybox' version '3.0.2' is up to date...
==> 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 (guest) => 8080 (host) (adapter 1)                                 
    default: 22 (guest) => 2222 (host) (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                                          
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.

Vagrant、VB 和 Windows 是最新版本。当 hypervisorlaunchtype 关闭时，Vagrant 可以正常运行。我必须暂时同时使用 Vagrant 和 Docker。

标签： dockervagrantvirtualboxhyper-v

解决方案

我为我的问题找到了解决方案：

v.customize ["modifyvm", :id, "--cableconnected1", "on"]

刚刚将它添加到 vagrantfile 中。

[编辑] 有时它运行得很快，有时运行需要几分钟，但有时它不运行并返回超时警告。

推荐阅读