sudo ifdown eth0 && sudo ifup eth0

之后,ifconfig显示eth0有一个IP地址.
然后我可以与流氓ssh连接
如果我通过VirtualBox管理器关闭guest虚拟机并启动guest虚拟机,客户端可以确定(使用IP地址),并且ifconfig显示eth0具有IP地址.
然后我可以与流氓ssh连接.

如果我通过VirtualBox管理器关闭并启动guest虚拟机,并且vagrant可以通过vagrant ssh进行连接.

如果我通过vagrant(流氓停止)和开机(vagrant up)关机,我得到相同的问题(超时在流氓侧,没有IP地址),并且无法通过vagrant ssh连接到guest虚拟机.

游客尝试连接时,客人显示：

cloud-init-nonet[4.54]: waiting 10 seconds for network device
cloud-init-nonet[14.57]: waiting 120 seconds for network device
cloud-init-nonet[134.57]: gave up waiting for a network device

我在客户端尝试了几个提出的解决方案,如this.

无论我尝试什么都没有帮助流浪汉方面.

在客户端的IP地址初始化修复后,VirtualBox管理员可以将该文件夹启动,现在几次,没有问题.
但是如果我通过vagrant(流氓停止)和开机(vagrant up)关机,我得到相同的超时问题,无法通过vagrant ssh连接到guest虚拟机.
我怀疑“vagrant up”清除网络接口并重新设置,在此过程中会导致问题重新出现.

(这也发生在guest：ubuntu / trusty32)

f:\Programs\HashiCorp\Vagrant\bin>vagrant up
Bringing machine 'vivid32' up with 'virtualBox' provider...
==> vivid32: Checking if Box 'ubuntu/vivid32' is up to date...
==> vivid32: Clearing any prevIoUsly set forwarded ports...
==> vivid32: Clearing any prevIoUsly set network interfaces...
==> vivid32: Preparing network interfaces based on configuration...
    vivid32: Adapter 1: nat
==> vivid32: Forwarding ports...
    vivid32: 22 => 2222 (adapter 1)
==> vivid32: Booting VM...
==> vivid32: Waiting for machine to boot. This may take a few minutes...
    vivid32: SSH address: 127.0.0.1:2222
    vivid32: SSH username: vagrant
    vivid32: SSH auth method: private key
    vivid32: Warning: Connection timeout. Retrying...
    vivid32: Warning: Connection timeout. Retrying...
...
    vivid32: 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.

>流浪者1.7.4
> VirtualBox – VirtualBox-5.0.0-101573
>主机 – Windows Vista
>访客ubuntu / vivid32