Package Details: vagrant-libvirt 0.1.2-1

Git Clone URL: (read-only, click to copy)
Package Base: vagrant-libvirt
Description: libvirt provider plugin for Vagrant
Upstream URL:
Licenses: MIT
Submitter: mtorromeo
Maintainer: IooNag
Last Packager: IooNag
Votes: 21
Popularity: 0.174897
First Submitted: 2016-12-02 14:08
Last Updated: 2020-07-19 07:31

Pinned Comments

mtorromeo commented on 2016-12-07 12:30

The plugin should still be installed using `vagrant plugin install vagrant-libvirt` as a normal user.
Vagrant will find all the required ruby gems already installed and will just mark the plugin as installed in `~/.vagrant.d/plugins.json` without compiling anything.

Latest Comments

1 2 Next › Last »

IooNag commented on 2018-11-05 20:09

With vagrant 2.2.0-2, the plugin fails to install:

Building native extensions. This could take a while... Traceback (most recent call last): 14: from /opt/vagrant/embedded/gems/gems/vagrant-2.2.0/bin/vagrant:164:in <main>' (...) 1: from /opt/vagrant/embedded/gems/gems/vagrant-2.2.0/plugins/commands/plugin/action/install_gem.rb:30:incall' /opt/vagrant/embedded/gems/gems/vagrant-2.2.0/lib/vagrant/plugin/manager.rb:156:in install_plugin': undefined methodname' for nil:NilClass (NoMethodError)

But using the full path to the gem file works fine: vagrant plugin install /opt/vagrant/embedded/gems/cache/vagrant-libvirt-0.0.45.gem

niya3 commented on 2018-07-20 19:55

  1. Do $ vagrant plugin install pkg-config pkg-config to skip pkg-config could not be used to find libxml-2.0 problem.

  2. Remove 'vagrant-libvirt' AUR package and install it via vagrant $ vagrant plugin install vagrant-libvirt to skip compilation problem.

84matte84 commented on 2018-06-27 06:41

Tried to follow all your suggestions without any success. Actually I am able to install vagrant-libvirt but I am not able to 'vagrant plugin install vagrant-libvirt' ...

hereafter the error log:

vagrant plugin install vagrant-libvirt Installing the 'vagrant-libvirt' plugin. This can take a few minutes... Building native extensions. This could take a while... Bundler, the underlying system Vagrant uses to install plugins, reported an error. The error is shown below. These errors are usually caused by misconfigured plugin installations or transient network issues. The error from Bundler is:

ERROR: Failed to build gem native extension.

current directory: ~/.vagrant.d/gems/2.5.1/gems/nokogiri-1.8.3/ext/nokogiri

/usr/bin/ruby -r ./siteconf20180627-27326-18p2wiw.rb extconf.rb checking if the C compiler accepts ... yes Building nokogiri using system libraries. pkg-config could not be used to find libxml-2.0 Please install either pkg-config or the pkg-config gem per

gem install pkg-config -v "~> 1.1"

pkg-config could not be used to find libxslt Please install either pkg-config or the pkg-config gem per

gem install pkg-config -v "~> 1.1"

pkg-config could not be used to find libexslt Please install either pkg-config or the pkg-config gem per

gem install pkg-config -v "~> 1.1"

ERROR: cannot discover where libxml2 is located on your system. please make sure pkg-config is installed. extconf.rb failed Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options.

Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/usr/bin/$(RUBY_BASE_NAME) --help --clean --use-system-libraries=true --with-zlib-dir --without-zlib-dir --with-zlib-include --without-zlib-include=${zlib-dir}/include --with-zlib-lib --without-zlib-lib=${zlib-dir}/lib --with-xml2-dir --without-xml2-dir --with-xml2-include --without-xml2-include=${xml2-dir}/include --with-xml2-lib --without-xml2-lib=${xml2-dir}/lib --with-libxml-2.0-config --without-libxml-2.0-config --with-pkg-config --without-pkg-config --with-xslt-dir --without-xslt-dir --with-xslt-include --without-xslt-include=${xslt-dir}/include --with-xslt-lib --without-xslt-lib=${xslt-dir}/lib --with-libxslt-config --without-libxslt-config --with-exslt-dir --without-exslt-dir --with-exslt-include --without-exslt-include=${exslt-dir}/include --with-exslt-lib --without-exslt-lib=${exslt-dir}/lib --with-libexslt-config --without-libexslt-config

To see why this extension failed to compile, please check the mkmf.log which can be found here:


extconf failed, exit code 1

Gem files will remain installed in ~/.vagrant.d/gems/2.5.1/gems/nokogiri-1.8.3 for inspection. Results logged to ~/.vagrant.d/gems/2.5.1/extensions/x86_64-linux/2.5.0/nokogiri-1.8.3/gem_make.out

thanks in advance for the help

dustball commented on 2018-01-27 17:04

The package is missing "ruby" from it's dependencies.

wyvie commented on 2017-08-17 20:54

Could you please fix the upload method?

Error while uploading image to storage pool: undefined method `upload' for #<Libvirt::StorageVol:0x00000717d5bc90>


wyvie commented on 2017-07-11 11:30

After the last update (11 Jul) I've been encountering this error on `vagrant up`:
Any ideas how to fix it?

Upd: managed to get it working after i altered the PKGBUILD:


Though something tells me it's not a very nice solution.

mtorromeo commented on 2017-06-21 11:13

@firecat53 see [1] and [2]. you can try to downgrade vagrant-substrate to 605.0566498-1 untile the issues are resolved.


firecat53 commented on 2017-06-20 22:50

Installed this package, then attempted to run `vagrant plugin install vagrant-libvirt` with this error:

Perhaps vagrant-mutate is missing?

vagrant init ubuntu/xenial64
Vagrant failed to initialize at a very early stage:

The plugins failed to initialize correctly. This may be due to manual
modifications made within the Vagrant home directory. Vagrant can
attempt to automatically correct this issue by running:

vagrant plugin repair

If Vagrant was recently updated, this error may be due to incompatible
versions of dependencies. To fix this problem please remove and re-install
all plugins. Vagrant can attempt to do this automatically by running:

vagrant plugin expunge --reinstall

Error message given during initialization: Unable to resolve dependency: user requested 'vagrant-mutate (> 0)'

Any ideas?

petRUShka commented on 2017-04-28 15:48

@wilga comment is very helpful. Please, @mtorromeo, update PKGBUILD accroding to that comment!

wilga commented on 2017-04-14 21:37

Works for me on current Arch (with ruby 2.4) with these 2 changes:

1. export CONFIGURE_ARGS="with-ldflags='-L/opt/vagrant/embedded/lib' with-libvirt-include=/usr/include with-libvirt-lib=/usr/lib"
2. save $PATH before gem-install loop, restore after

No clean chroot required.