Vagrant up 不起作用，不返回任何错误（Windows 7）

Question

我正在开发一个在 Roots WP 堆栈上运行的网站，我们现在正计划从 xampp 切换到 vagrant。问题是当我运行“vagrant up”时，什么也没有发生。没有错误，没有任何输出，它只是挂起，直到我退出命令。运行 vagrant init 会创建一个 vagrantfile，但 vagrant up 绝对不会做任何事情。

我现在在工作计算机上使用 Windows 7。我过去曾成功使用过 vagrant，没有任何问题。

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

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.

  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://vagrantcloud.com/search.
  config.vm.box = "precise32"

  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.
  config.vm.box_url = "http://files.vagrantup.com/precise32.box"

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # NOTE: This will enable public access to the opened port
  # config.vm.network "forwarded_port", guest: 80, host: 8080

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine and only allow access
  # via 127.0.0.1 to disable public access
  # config.vm.network "forwarded_port", guest: 80, host: 8080, host_ip: "127.0.0.1"

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network "private_network", ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network "public_network"

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider "virtualbox" do |vb|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true
  #
  #   # Customize the amount of memory on the VM:
  #   vb.memory = "1024"
  # end
  #
  # View the documentation for the provider you are using for more
  # information on available options.

  # Enable provisioning with a shell script. Additional provisioners such as
  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
  # documentation for more information about their specific syntax and use.
  # config.vm.provision "shell", inline: <<-SHELL
  #   apt-get update
  #   apt-get install -y apache2
  # SHELL
end

Answer 1

我也遇到过同样的问题（Windows7 Pro SP1、VirtualBox 5.1.26、vagrant 1.9.7）。 我已经通过将 vagrant 降级到 1.9.6 解决了这个问题。

Answer 2

如果 Vagrant 命令在 Windows 上挂起是因为它们正在与 VirtualBox 通信，这可能是由 VirtualBox 的权限问题引起的。这很容易解决。以普通用户或管理员身份启动 VirtualBox 将阻止您以相反的方式使用它。请记住，当 Vagrant 与 VirtualBox 交互时，它会以与运行 Vagrant 的控制台相同的访问级别与之交互。

要解决此问题，请完全关闭所有 VirtualBox 机器和 GUI。等待几秒钟。然后，仅使用您希望使用的访问级别启动 VirtualBox..

Answer 3

由于在 vagrant 中调用 powershell 而存在问题。这仍然是当前 (2.0.1) vagrant 版本的问题。

相关link.

有多种解决方案：

• 将 vagrant 降级到 1.9.6
• 将 powershell 更新到更高版本

Answer 4

我也有类似的问题。 我的环境是 Vagrant 2.0.2 ， virtualbox 5.2.6 和 win 7。 我终于通过将 powershell 2 更新为 powershell 4 来解决它。