我正在开发一个在Roots WP堆栈上运行的网站，我们现在计划从xampp切换到vagrant。问题是当我运行"流浪者"时，什么也没发生。没有错误，没有任何输出，它只是挂起，直到我退出命令。运行 vagrant init 会创建一个 vagrant file，但 vagrant up 绝对什么都不做。
我现在正在一台工作计算机上使用Windows 7。我过去曾成功地使用流浪者，没有问题。
# -*- 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
我遇到了同样的问题(Windows7 Pro SP1，VirtualBox 5.1.26，vagrant 1.9.7(。 我已经通过将流浪者降级到 1.9.6 来解决此问题。
如果Vagrant命令因为与VirtualBox通信而挂在Windows上，这可能是由VirtualBox的权限问题引起的。这很容易解决。以普通用户或管理员身份启动VirtualBox将阻止您以相反的方式使用它。请记住，当Vagrant与VirtualBox交互时，它将以与运行Vagrant的控制台相同的访问级别与之交互。
要解决此问题，请完全关闭所有VirtualBox机器和GUI。等待几秒钟。然后，仅使用您希望使用的访问级别启动VirtualBox。
由于在流浪中调用Powershell而存在问题。这仍然是当前 (2.0.1( 流浪版本的问题。
相关链接。
有多种解决方案：
- 将流浪者降级到 1.9.6
- 将电源外壳更新到更高版本
我也有类似的问题。 我的环境是Vagrant 2.0.2，virtualbox 5.2.6和win 7。 我最终通过将Powershell 2更新为Powershell 4来解决它。