Vagrant Libvirt Provider

This is a Vagrant 1.1+ plugin that adds an Libvirt provider to Vagrant, allowing Vagrant to control and provision machines via Libvirt toolkit.

Note: Actual version (0.0.4) is still a development one. Feedback is welcome and can help a lot :-)

Features (Version 0.0.4)

  • Vagrant up, destroy, suspend, resume, halt, ssh and provision commands.
  • Upload box image (qcow2 format) to Libvirt storage pool.
  • Create volume as COW diff image for domains.
  • Create and boot Libvirt domains.
  • SSH into domains.
  • Provision domains with any built-in Vagrant provisioner.
  • Minimal synced folder support via rsync.

Future work

  • More boxes should be available.
  • Take a look at open issues.


Install using standard Vagrant 1.1+ plugin installation methods. After installing, vagrant up and specify the libvirt provider. An example is shown below.

$ vagrant plugin install vagrant-libvirt

Possible problems with plugin installation

In case of problems with building nokogiri and ruby-libvirt gem, install missing development libraries for libxslt, libxml2 and libvirt.

In Ubuntu, Debian, ...

$ sudo apt-get install libxslt-dev libxml2-dev libvirt-dev

In RedHat, Centos, Fedora, ...

# yum install libxslt-devel libxml2-devel libvirt-devel

Vagrant Project Preparation

After installing the plugin (instructions above), the quickest way to get started is to add Libvirt box and specify all the details manually within a config.vm.provider block. So first, add Libvirt box using any name you want. This is just an example of Libvirt CentOS 6.4 box available:

$ vagrant box add centos64

And then make a Vagrantfile that looks like the following, filling in your information where necessary.

Vagrant.configure("2") do |config|
  config.vm.define :test_vm do |test_vm| = "centos64"

  config.vm.provider :libvirt do |libvirt|
    libvirt.driver = "qemu" = ""
    libvirt.connect_via_ssh = true
    libvirt.username = "root"
    libvirt.storage_pool_name = "default"

Libvirt Configuration Options

This provider exposes quite a few provider-specific configuration options:

  • driver - A hypervisor name to access. For now only qemu is supported.
  • host - The name of the server, where libvirtd is running.
  • connect_via_ssh - If use ssh tunnel to connect to Libvirt.
  • username - Username and password to access Libvirt.
  • password - Password to access Libvirt.
  • storage_pool_name - Libvirt storage pool name, where box image and instance snapshots will be stored.

Domain Specific Options

  • memory - Amount of memory in MBytes. Defaults to 512 if not set.
  • cpus - Number of virtual cpus. Defaults to 1 if not set.

Specific domain settings can be set for each domain separately in multi-VM environment. Example below shows a part of Vagrantfile, where specific options are set for dbserver domain.

Vagrant.configure("2") do |config|
  config.vm.define :dbserver do |dbserver| = "centos64"
    dbserver.vm.provider :libvirt do |domain|
      domain.memory = 2048
      domain.cpus = 2


Create Project - Vagrant up

In prepared project directory, run following command:

$ vagrant up --provider=libvirt

Vagrant needs to know that we want to use Libvirt and not default VirtualBox. That's why there is --provider=libvirt option specified. Other way to tell Vagrant to use Libvirt provider is to setup environment variable export VAGRANT_DEFAULT_PROVIDER=libvirt.

How Project Is Created

Vagrant goes through steps below when creating new project:

  1. Connect to Libvirt localy or remotely via SSH.
  2. Check if box image is available in Libvirt storage pool. If not, upload it to remote Libvirt storage pool as new volume.
  3. Create COW diff image of base box image for new Libvirt domain.
  4. Create and start new domain on Libvirt host.
  5. Check for DHCP lease from dnsmasq server.
  6. Wait till SSH is available.
  7. Sync folders via rsync and run Vagrant provisioner on new domain if setup in Vagrantfile.


Networking features in the form of are not supported right now. Support for private network is planned to be added in next release of provider.

Obtaining Domain IP Address

Libvirt doesn't provide standard way how to find out an IP address of running domain. But we know, what is MAC address of virtual machine. Libvirt is closely connected with dnsmasq server, which acts also as a DHCP server. Dnsmasq server makes lease information public in /var/lib/libvirt/dnsmasq directory, or in /var/lib/misc/dnsmasq.leases file on some systems. This is the place, where information like which MAC address has which IP address resides and it's parsed by vagrant-libvirt plugin.

Synced Folders

There is minimal support for synced folders. Upon vagrant up, the Libvirt provider will use rsync (if available) to uni-directionally sync the folder to the remote machine over SSH.

This is good enough for all built-in Vagrant provisioners (shell, chef, and puppet) to work!

Box Format

You can view an example box in the example_box/directory. That directory also contains instructions on how to build a box.

The box is a tarball containing:

  • qcow2 image file named box.img.
  • metadata.json file describing box image (provider, virtual_size, format).
  • Vagrantfile that does default settings for the provider-specific configuration for this provider.


To work on the vagrant-libvirt plugin, clone this repository out, and use Bundler to get the dependencies:

$ git clone
$ cd vagrant-libvirt
$ bundle install

Once you have the dependencies, verify the unit tests pass with rake:

$ bundle exec rake

If those pass, you're ready to start developing the plugin. You can test the plugin without installing it into your Vagrant environment by just creating a Vagrantfile in the top level of this directory (it is gitignored) that uses it. Don't forget to add following line at the beginning of your Vagrantfile while in development mode:

Vagrant.require_plugin "vagrant-libvirt"

Now you can use bundler to execute Vagrant:

$ bundle exec vagrant up --provider=libvirt


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request