Provider: Hyper-V, Provider Expected: virtualbox

1,548 views
Skip to first unread message

Eric Sepich

unread,
May 19, 2014, 11:46:24 PM5/19/14
to vagra...@googlegroups.com
My OS is Windows 8.1. I have attached my Vagrantfile. I am getting some messaging about the provider coming out of the console:

Provider expected: hyperv
Provider of box: virtualbox
PS C:\Users\Eric\ZF2-Vagrant> git submodule update --init --recursive
PS C:\Users\Eric\ZF2-Vagrant> vagrant up
Bringing machine 'default' up with 'hyperv' provider...
==> default: Verifying Hyper-V is enabled...
==> default: Box 'ubuntu-12.04' could not be found. Attempting to find and install...
    default: Box Provider: hyperv
    default: Box Version: >= 0
==> default: Adding box 'ubuntu-12.04' (v0) for provider: hyperv
    default: Downloading: http://files.vagrantup.com/precise64.box
    default: Progress: 100% (Rate: 3551k/s, Estimated time remaining: --:--:--)
The box you attempted to add doesn't match the provider you specified.

Provider expected: hyperv
Provider of box: virtualbox
aPS C:\Users\Eric\ZF2-Vagrant>

What is this message about?

Thank you...

Vagrantfile:
Vagrant.configure("2") do |config|
  config.vm.synced_folder "~/source-api", "/var/source-api"
  config.vm.synced_folder "~/source-client", "/var/source-client"
  
  config.vm.box = "ubuntu-12.04"
  config.vm.network :private_network, ip: "192.168.56.2"
  config.vm.provider :virtualbox do |vb|
    vb.customize ["modifyvm", :id, "--memory", "1024"]
  end
  
  config.vm.provision :chef_solo do |chef|
    chef.cookbooks_path = "./cookbooks"
    
    chef.add_recipe "apt"
    chef.add_recipe "custom::dotdeb"
    chef.add_recipe "mysql::server"
    chef.add_recipe "nginx"
    chef.add_recipe "php"
    chef.add_recipe "php-fpm"
    chef.add_recipe "custom::fpm-config"
    chef.add_recipe "php::module_curl"
    chef.add_recipe "php::module_gd"
    chef.add_recipe "php::module_mysql"
    chef.add_recipe "postfix"
    chef.add_recipe "custom::db"
    chef.add_recipe "custom::hosts"
    chef.add_recipe "custom::vhosts"
    chef.add_recipe "custom::mysql_permissions"
    chef.add_recipe "custom::restart_services"
    
    chef.json = {
      :mysql => {
        :server_root_password => "root",
        :server_repl_password => "repl",
        :server_debian_password => "debian",
        :bind_address => '0.0.0.0'
      },
      :nginx => {
        :default_site_enabled => false
      },
      :php => {
        :directives => {
          'pdo_mysql.default_socket' => '/var/run/mysqld/mysqld.sock',
          'mysql.default_socket' => '/var/run/mysqld/mysqld.sock',
          'mysqli.default_socket' => '/var/run/mysqld/mysqld.sock',
          'date.timezone' => 'Europe/London'
        }
      }
    }
  end
end






Mitchell Hashimoto

unread,
May 20, 2014, 12:30:51 AM5/20/14
to vagra...@googlegroups.com
The URL for the box you specified is only for VirtualBox. If you want
a Hyper-V box, use "hashicorp/precise64"
> --
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Eric Sepich

unread,
May 20, 2014, 2:56:00 AM5/20/14
to vagra...@googlegroups.com
I tried using VirtualBox without Hyper-V installed. It didn't work with the Vagrantfile and there was some output that stated that Hyper-V needs to be installed. That's what prompted me to install Hyper-V. Really what I wanted to accomplish is do a vagrant up without modifying the Vagrantfile. Is there some way to specify to use virtualbox instead of Hyper-V?

Thank you for your reply. I'll try with "hashicorp/precise64" as well.


You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/IPRUebdn-Lw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.

Alvaro Miranda Aguilera

unread,
May 20, 2014, 4:46:16 PM5/20/14
to vagra...@googlegroups.com
if there is no variable like VAGRANT_DEFAULT_PROVIDER or is no vagrantfile on your home/.vagrant.d/Vagrantfile

that is forcing hyper-v then the "automagically" discover is causing issues..

What happen if you do

vagrant up --provider=virtualbox


Eric Sepich

unread,
May 20, 2014, 6:36:13 PM5/20/14
to vagra...@googlegroups.com
Vagrant is telling me that it can not detect virtualbox

Windows PowerShell
Copyright (C) 2013 Microsoft Corporation. All rights reserved.

PS C:\Windows\system32> cd ~/ZF2-Vagrant
PS C:\Users\Eric\ZF2-Vagrant> vagrant up --provider=virtualbox
The provider 'virtualbox' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:

Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires
this to be available on the PATH. If VirtualBox is installed, please find the
`VBoxManage` binary and add it to the PATH environmental variable.
PS C:\Users\Eric\ZF2-Vagrant>

Alvaro Miranda Aguilera

unread,
May 20, 2014, 6:41:35 PM5/20/14
to vagra...@googlegroups.com
what happen if you try from a non-powershell setup?

say cmd or any bash from cygwin or anywhere?

I use the bash that came in github client..

Eric Sepich

unread,
May 20, 2014, 7:27:26 PM5/20/14
to vagra...@googlegroups.com
I tried with cmd and GitBash. I added VBoxManage to my path as well. Running a quick VBoxManage from arbitrary path I see its output there. It appears virtualbox is not being detected as a provider.aa


Alvaro Miranda Aguilera

unread,
May 20, 2014, 7:49:59 PM5/20/14
to vagra...@googlegroups.com


--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages