我有一个Ubuntu14.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上工作?
编辑:问题是Windows关闭了以前在我的系统上打开的端口,在我更新到秋季创建者更新之前,特别是在本例中是端口22。我创建了一个异常以允许端口22通过,现在它可以正常工作了。
发布于 2018-04-24 02:18:45
运行Windows7时,我遇到了同样的问题。在superuser.com上尝试这种推荐
发布于 2017-12-11 06:18:04
我认为您的BIOS上没有启用虚拟化。
检查以下内容:任务管理器>性能tab>虚拟化或通过CMD的系统信息。
如有残疾
查看如何从BIOS启用它,基于您的硬件制造。
如果启用
然后尝试从“添加或删除windows功能”中禁用"Hyper-V“。
您还可以尝试从Virtualbox手动启动64位vm,这可能告诉您机器处于“未知状态”的原因
另外,尝试使用以下配置创建一个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。
https://stackoverflow.com/questions/47744174
复制相似问题