windows 10 更新后 vagrant up 停止工作
vagrant up stopped working after windows 10 update
最近 Windows 10 更新后,我的流浪虚拟机停止工作,拒绝在 vagrant up
启动。这个问题似乎与我用于虚拟机的 Virtualbox 提供程序有关,并且只有在 Vagrantfile 中配置了 private_network 时才会出现,而端口转发和 public_network
似乎都有效。
我第一次将操作系统从 Windows 7 更新到 Windows 10 时就遇到了类似的问题。在那种情况下,我用 Virtualbox 的 [=19] 的补丁解决了这个问题=];但是,应用新的 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
我遇到了完全相同的问题。在此博客上找到的解决方案有帮助:
http://codeworks.it/blog/?p=329
基本上,更新后,Windows "magically" 从 VirtualBox Host-Only Network 关闭了 VirtualBox NDIS6 Bridged Networking Driver。
要修复它您应该在 Windows:
中检查您的网络接口
- 在 VirtualBox Host-Only Network 属性中,请检查 VirtualBox 是否
NDIS6 桥接网络驱动程序被勾选。
- 如果没有 - 打勾 :)
去看看这是否有帮助,我敢打赌它会 ;)
Go to "Control Panel" -> "Network and Internet" -> "Network Connections"
Right Click on "VirtualBox Host-Only Network #4" -> properties.
这就是您将看到的window。
现在有 2 个选项,"VirtualBox NDIS6 Bridged Networking Driver" 是否选中。
如果不是,您可以检查一下,它就可以解决问题。
但如果选中,则需要重新安装 VirtualBox 版本。
最近 Windows 10 更新后,我的流浪虚拟机停止工作,拒绝在 vagrant up
启动。这个问题似乎与我用于虚拟机的 Virtualbox 提供程序有关,并且只有在 Vagrantfile 中配置了 private_network 时才会出现,而端口转发和 public_network
似乎都有效。
我第一次将操作系统从 Windows 7 更新到 Windows 10 时就遇到了类似的问题。在那种情况下,我用 Virtualbox 的 [=19] 的补丁解决了这个问题=];但是,应用新的 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
我遇到了完全相同的问题。在此博客上找到的解决方案有帮助: http://codeworks.it/blog/?p=329
基本上,更新后,Windows "magically" 从 VirtualBox Host-Only Network 关闭了 VirtualBox NDIS6 Bridged Networking Driver。
要修复它您应该在 Windows:
中检查您的网络接口- 在 VirtualBox Host-Only Network 属性中,请检查 VirtualBox 是否 NDIS6 桥接网络驱动程序被勾选。
- 如果没有 - 打勾 :)
去看看这是否有帮助,我敢打赌它会 ;)
Go to "Control Panel" -> "Network and Internet" -> "Network Connections"
Right Click on "VirtualBox Host-Only Network #4" -> properties.
这就是您将看到的window。
现在有 2 个选项,"VirtualBox NDIS6 Bridged Networking Driver" 是否选中。
如果不是,您可以检查一下,它就可以解决问题。
但如果选中,则需要重新安装 VirtualBox 版本。