Windows 7 为什么流浪汉不能在Windows7上开箱即用?

Windows 7 为什么流浪汉不能在Windows7上开箱即用?,windows-7,vagrant,virtualization,Windows 7,Vagrant,Virtualization,这里是64位的Windows7。他去了医院。下载Windows 64位安装程序,使用所有推荐的默认值安装,然后重新启动 然后读他们的文章。打开命令提示符: vagrant init hashicorp/precise32 并查看以下输出: A `Vagrantfile` has been placed in this directory. You are now ready to `vagrant up` your first virtual environment! Please read

这里是64位的Windows7。他去了医院。下载Windows 64位安装程序,使用所有推荐的默认值安装,然后重新启动

然后读他们的文章。打开命令提示符:

vagrant init hashicorp/precise32
并查看以下输出:

A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
嗯。到现在为止,一直都还不错。那么我会:

vagrant up
以下是输出:

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'hashicorp/precise32' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Loading metadata for box 'hashicorp/precise32'
    default: URL: https://atlas.hashicorp.com/hashicorp/precise32
==> default: Adding box 'hashicorp/precise32' (v1.0.0) for provider: virtualbox
    default: Downloading: https://atlas.hashicorp.com/hashicorp/boxes/precise32/versions/1.0.0/providers/virtualbox.box
    default:
==> default: Successfully added box 'hashicorp/precise32' (v1.0.0) for 'virtualbox'!
==> default: Importing base box 'hashicorp/precise32'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'hashicorp/precise32' is up to date...
==> default: Setting the name of the VM: vms_default_1421176231425_15801
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 => 2222 (adapter 1)
==> 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: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Remote connection disconnect. 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.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
然后我阅读了《入门指南》的下一部分:

现在想象一下,你曾经做过的每一个项目都这么容易设置

LOL


为什么会出现此错误?

要进行故障排除和/或使虚拟机正常工作,您可以尝试。这可能有助于提供一条线索,说明为什么它不能立即正常工作。谢谢@BrianC(+1)-但是我在
vagrant文件中取消了这段代码的注释(以启用GUI模式),然后重新运行
vagrant up
,没有什么不同。思想?再次感谢!我很震惊,这没有得到更多的关注!这是一个主要的工具,只是没有功能,甚至没有最低的生存能力…Hashicorp?布勒?Bueller?你有没有可能安装了Hyper-V?@smeeb我使用的Vagrant主要来自Mac,也来自Windows。有时,我会遇到一些特定于Windows的问题,但在大多数情况下,它“只是起作用”。在我的Win7笔记本电脑上,我只是按照你的确切步骤操作,它对我起了作用。您可以检查这个问题“”,它有很多可能的解决方案。首先,我要检查您的PC BIOS中是否启用了虚拟化。像MichaelS建议的那样手动启动VirtualBox也会得到证实。