Question

在最近的Windows 10更新后，我的流浪虚拟机停止工作，拒绝从vagrant up开始。问题似乎与我用于我的VM的Virtualbox提供程序有关，并且只有在Vagrantfile中配置了private_network时才会出现问题，而端口转发和public_network似乎都有效。

我第一次将操作系统从Windows 7更新到Windows 10时，我遇到了类似的问题。在这种情况下，我解决了Virtualbox＆＃39; s ticket 14040中补丁的问题;但是，在应用新的Windows更新后，补丁解决方案不再有效。

我还尝试将VirtualBox和Vagrant更新到他们的最新版本，但这并没有改变任何内容。

以下是我的Windows / Virtualbox / Vagrant版本：

Microsoft Windows 10 version 1511 (build SO 10586.14)
VirtualBox version 5.0.10 r104061
Vagrant version 1.7.4

这是我在启动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...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.

以下是Virtualbox在尝试从Virtualbox用户界面启动VM时显示的错误：

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #15' (VERR_INTNET_FLT_IF_NOT_FOUND).
Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Codice 'uscita: 
E_FAIL (0x80004005)
Componente: 
ConsoleWrap
Interfaccia: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

最后，这里是我的Vagrantfile的相关部分;如上所述，如果我评论private_network行，则机器启动：

# -*- mode: ruby -*-
# vi: set ft=ruby :

VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
    config.vm.box = "ubuntu-14.04-amd64-docker"
      config.vm.box_url = "https://github.com/jose-lpa/packer-ubuntu_14.04/releases/download/v2.0/ubuntu-14.04.box"
      config.vm.hostname = "falcon.staging"
    config.vm.network "private_network", ip: "192.168.33.114"
    config.vm.provider "virtualbox" do |vb|
        vb.gui = false
        vb.memory = "2048"
    end
    ...
end

Answer 1

我遇到了完全相同的问题。此博客上的解决方案有助于： http://codeworks.it/blog/?p=329

基本上，在更新之后，Windows＆＃34;神奇地＆＃34;从VirtualBox Host-Only网络关闭 VirtualBox NDIS6桥接网络驱动程序。

要修复它您应该检查Windows中的网络接口：

在VirtualBox Host-Only Network属性中，请检查VirtualBox是否正确已勾选NDIS6桥接网络驱动程序。
如果没有 - 勾选它：）

去检查一下是否有帮助，我打赌它会;）

Answer 2

转到＆＃34;控制面板＆＃34; - ＆GT; ＆＃34;网络和互联网＆＃34; - ＆GT; ＆＃34;网络连接＆＃34;

右键单击＆＃34; VirtualBox Host-Only Network＃4＆＃34; - ＆GT;属性。

这是您将看到的窗口。

现在有两个选项，＆＃34; VirtualBox NDIS6桥接网络驱动程序＆＃34;是否检查。
如果不是，你可以检查它，它会起作用但如果检查过，您需要重新安装VirtualBox版本。

在Windows 10更新后，vagrant up停止工作

2 个答案: