Jeżeli podczas vagrant up dostanie się taki komunikat:

~/.vagrant.d/gems/2.4.4/gems/vagrant-ovirt-0.0.2/lib/vagrant-ovirt.rb:44:in `default_provider': wrong number of arguments (given 1, expected 0) (ArgumentError)
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/plugin/v2/command.rb:177:in `block in with_target_vms'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/plugin/v2/command.rb:204:in `block in with_target_vms'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/plugin/v2/command.rb:186:in `each'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/plugin/v2/command.rb:186:in `with_target_vms'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/plugins/commands/up/command.rb:87:in `execute'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/cli.rb:58:in `execute'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/lib/vagrant/environment.rb:291:in `cli'
from C:/HashiCorp/Vagrant/embedded/gems/2.2.3/gems/vagrant-2.2.3/bin/vagrant:182:in `<main>'

Można obejść to na dwa sposoby:

vagrant up –provider virtualbox

lub

zmieniając w pliku ~/.vagrant.d/gems/2.4.4/gems/vagrant-ovirt-0.0.2/lib/vagrant-ovirt.rb w linii 44:

def default_provider

na

def self.default_provider