-
Notifications
You must be signed in to change notification settings - Fork 511
Vagrant fails with "libvirt is not a recognized provider" #770
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
seeing the same thing. Versions
|
#769 will fix this issue for the time being this works
|
Thank you. It solved the issue. |
Just to add to the above workaround. I didn't have ruby installed natively on my system, so I used the gem binary located at I don't know if there are any downsides to doing this, but I didn't want to install and configure ruby to get this right. Gem file that was generated was named differently as Apologies if anything I've mentioned here is incorrect, my experience with ruby is very limited. |
Issue is fixed on Debian 8.8 with vagrant-libvirt (0.0.40) installed in the way proposed by timhughes: But new dhcp leases issue has been detected #674 and temporary fixed with the workaround proposed by mrvovanness here fog/fog-libvirt#28 |
Can you please retest with 1.9.7? |
I have the same issue with Vagrant 1.9.7. The output when installing the .gem > gem_make.txt
Could easily be an issue on my system (Fedora 26), but if you do know a possible solution I would love to try it out. |
Looking at your 4th step, where are you getting the |
@HartS reasonably sure it's a type and should have been |
I had the same issue on my Fedora 26. No solutions was working except one, taken from ArchLinux Vagant wiki: https://wiki.archlinux.org/index.php/Vagrant#vagrant-libvirt. Package libvirt-devel is required. Vagrant package: vagrant-2.0.0-1.x86_64 |
libvirt-dev for debian/ubuntu users |
Running Debian 9 (Stretch) and installing |
This was fixed in #769 so this ticket can be closed |
Uh oh!
There was an error while loading. Please reload this page.
I do have strange behavior with vagrant-libvirt plugin on Centos 6.8, libvirt v0.10.2.
Steps to reproduce
vagrant plugin install vagrant-libvirt
. The strange thing here, that plugin is version 0.0.20.vagrant init
.vagrant up --provisioner=libvirt
Expected behaviour
VM up and running
Actual behaviour
Below stacktrace:
vagrant up --provider=libvirt
/root/.vagrant.d/gems/2.2.5/gems/fog-core-1.43.0/lib/fog/core/services_mixin.rb:12:in
'new': libvirt is not a recognized provider (ArgumentError) from /root/.vagrant.d/gems/2.2.5/gems/fog-core-1.43.0/lib/fog/compute.rb:54:in
new'from /root/.vagrant.d/gems/2.2.5/gems/vagrant-libvirt-0.0.20/lib/vagrant-libvirt/action/connect_libvirt.rb:38:in
call' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/action/warden.rb:34:in
call'from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/action/builtin/config_validate.rb:25:in
call' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/action/warden.rb:34:in
call'from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/action/builder.rb:116:in
call' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/action/runner.rb:66:in
block in run'from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/util/busy.rb:19:in
busy' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/action/runner.rb:66:in
run'from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/machine.rb:225:in
action_raw' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/machine.rb:200:in
block in action'from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/environment.rb:567:in
lock' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/machine.rb:186:in
call'from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/machine.rb:186:in
action' from /root/.vagrant.d/gems/2.2.5/gems/vagrant-libvirt-0.0.20/lib/vagrant-libvirt/provider.rb:58:in
state'from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/machine.rb:506:in
state' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/machine.rb:145:in
initialize'from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/vagrantfile.rb:79:in
new' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/vagrantfile.rb:79:in
machine'from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/environment.rb:669:in
machine' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/plugin/v2/command.rb:177:in
block in with_target_vms'from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/plugin/v2/command.rb:201:in
call' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/plugin/v2/command.rb:201:in
block in with_target_vms'from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/plugin/v2/command.rb:183:in
each' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/plugin/v2/command.rb:183:in
with_target_vms'from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commands/up/command.rb:131:in
install_providers' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/commands/up/command.rb:85:in
execute'from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/cli.rb:42:in
execute' from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/environment.rb:308:in
cli'from /opt/vagrant/embedded/gems/gems/vagrant-1.9.4/bin/vagrant:127:in `
System configuration
OS/Distro version:: Centos 6.8
Libvirt version: v0.10.2
Output of
vagrant version; vagrant plugin list
:`vagrant version
Installed Version: 1.9.4
Latest Version: 1.9.4
You're running an up-to-date version of Vagrant!
vagrant plugin list
vagrant-libvirt (0.0.20)
vagrant-share (1.1.7)
`
Output of
VAGRANT_LOG=debug vagrant ... --provider=libvirt
The same as above stacktrace.
``
A Vagrantfile to reproduce the issue:
The text was updated successfully, but these errors were encountered: