Question

我有一个Ubuntu 14.04 Vagrant框，我试图在Windows 10主机上使用。

该框不是问题，因为它在其他系统上运行良好。

我的Virtualbox版本目前是5.1.28，我尝试了最新版本，这是问题何时开始，所以我回滚到5.1.28，希望能解决它，但无济于事。

我的Vagrant版本是2.0.0。

这是我运行vagrant up

时得到的结果

λ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'dev_box'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: Dev_default_1512943736797_96012
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: bridged
==> default: Forwarding ports...
    default: 3000 (guest) => 3000 (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
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'unknown' 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 / Vagrant在Windows 10上运行？

编辑：问题是在我更新到Fall Creators Update之前，Windows防火墙已关闭先前在我的系统上打开的端口，特别是在本例端口22中。我创建了一个例外以允许端口22通过，现在它按预期工作。

Answer 1

运行Windows7我遇到了同样的问题。在superuser.com上试试这个推荐文件

https://superuser.com/questions/936581/how-to-config-windows-firewall-so-vm-host-only-can-ping-windows-7

Answer 2

我认为你的BIOS没有启用虚拟化。

检查：任务管理器＆gt;效果标签＆gt;虚拟化或通过CMD的 systeminfo

如果已停用：

根据您的硬件制作，查看如何从BIOS启用它。

如果启用：

然后尝试禁用＆＃34; Hyper-V＆＃34;来自＆＃34;添加或删除Windows功能＆＃34;

您也可以尝试从Virtualbox手动启动64位vm，这可能会告诉您机器处于＆＃34;未知状态＆＃34;

背后的原因

另外，尝试使用以下配置创建Vagrant文件（使用32位操作系统）：

Vagrant.configure(2) do |config|
  config.vm.box = "hashicorp/precise32"
  config.vm.box_download_insecure = true #true just to bypass ssl validation error (strict no for production)
end

尝试从同一目录运行vagrant up。

由于Windows防火墙Virtualbox无法连接，Vagrant无法启动

2 个答案: