vagrant-kvm 0.1.4 → 0.1.5

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 050ef979981ce83ec1d1afe226a6f4b7f6da29d9
+  data.tar.gz: 95b009356ebd8e0058e2ba18b2debaa43e2015ad
+SHA512:
+  metadata.gz: 34a150ca16164e872cd72291c846312013346c659f22bf680f213c877477f9c404e46a5beb5c2dff16955bbb5e2b0b6efc6a8fb80a2eb8112230caf4f7bfbdd1
+  data.tar.gz: 0f8761c309f8f5b4acdcc11068300266bcbfacb306c167b65dc869e3818bd8cd55b8478357d9d6c73044feaa0246208c5ef6ab51904740dfc6e8aa84e424bb47

data/.gitignore

@@ -12,3 +12,5 @@ Gemfile.lock
 .vagrant
 Vagrantfile
 !example_box/Vagrantfile
+.rvmrc
+*.box

data/.rspec

@@ -0,0 +1 @@
+--color

data/.travis.yml

@@ -0,0 +1,14 @@
+language: ruby
+before_install:
+  - sudo add-apt-repository -y ppa:miurahr/vagrant
+  - sudo apt-get update -qq
+  - sudo apt-get install -qq libvirt-dev libvirt-bin qemu-kvm qemu
+  - gem install --version '~> 1.5.2' bundler
+rvm:
+  - 2.0.0
+script:
+  - export rvmsudo_secure_path=1
+  - rvmsudo ruby --version
+  - rvmsudo gem --version
+  - rvmsudo bundle --version
+  - rvmsudo bundle exec rspec spec/vagrant-kvm/

data/CHANGELOG.md

@@ -1,3 +1,32 @@
+# 0.1.5 (March 22, 2014)
+
+* Change default box format to qcow2 [GH-63]
+* Support Vagrant 1.4.0+[GH-126]
+* Remove VMDK conversion. It is now supported by vagrant-mutate[GH-105]
+* Add support for configuration for memory/cpu [GH-54][GH-51][GH-68]
+* Add support for gui configuration [GH-41][GH-53]
+* Add support for 'vagrant package' [GH-69]
+* Add support for port forwarding [GH-72]
+* Speed-up by copy-on-write backing disk image [GH-63]
+* VNC port/auth configuration[GH-116][GH-84]
+* SATA/IDE disk support[GH-110]
+* Respect disabled directive on synced_folder configuration [GH-65]
+* Configuration options for video and networks[GH-101]
+* Configuration option for disk_bus[GH-80]
+* Fixes storage pool permission issue.[GH-130][GH-154]
+* Add document how to avoid a permission error in Fedora/Arch [GH-163][GH-171]
+* Fixes segment fault when VirtualBox installed [GH-57][GH-66]
+* Making a path of qemu binary specifiable [GH-59]
+* Fixes error when box has not private network defition[GH-70]
+* Add Japanese error messages translation [GH-71]
+* Add check for kvm kernel module and loading if needed [GH-67]
+* Improve error handling [GH-50]
+* Expanded/Fixes Readme file [GH-55]
+* Add spec test and TravisCI test[GH-82]
+* Resume network when resume from suspend[GH-134]
+* Fixes error when suspending with SATA drive[GH-176]
+* Search qemu/kvm binary in new qemu-system-* filename[GH-109]
+
 # 0.1.4 (August 20, 2013)
 
 * Add support for qcow2 and configuration for image type [GH-45]

data/DEVELOPMENT.md

@@ -0,0 +1,87 @@
+# Development Note
+
+Supported ruby version is 2.0.x on vagrant 1.4.0 and later.
+You may need to use a recent OS version for development base
+such as Ubuntu Saucy(13.10), Trusy(14.04) or Fedora 19,20.
+
+If you're Mac user and you have Vagrant and VMware Fusion,
+you can use bundled box for development.
+
+If you're Linux user(of cource, you try to use KVM),
+You are lucky to run development version of vagrant-kvm on Vagrant,
+QEMU/KVM and vagrant-kvm itself.
+
+Unfortunately VirtualBox don't support nested virtualization.
+We cannot use it for vagrant-kvm development.
+
+## Requirement
+
+This plugin requires additional packages for development.
+
+- For source:
+ * `git`
+
+- For KVM:
+ * `qemu-utils` `libvirt-dev`
+
+- For File share:
+ * `apparmor-utils` (Ubuntu)
+
+- For Ruby:
+ * `ruby2.0` `ruby2.0-dev` `libxml2-dev` `libxslt-dev`
+ * gems: `rake` `bundler`
+ 
+- For box development:
+ * `bsdtar` `libguestfs-tools`
+
+It is better to use `rvm` or `rbenv` to control ruby version as same as one
+vagrant bundled.
+
+## Test vagrant-kvm with vagrant-kvm
+
+You can run vagrant-kvm on kvm/qemu guest OS with vagrant-kvm.
+It is required to run KVM with 64bit Operating System and configure
+`kvm-intel` or `kvm-amd` kernel module to allow it.
+
+Please add a file and reboot in order to use kvm with nested virtulization support.
+
+/etc/modprobe.d/kvm.conf:
+```
+options kvm-intel nested=1
+options kvm-amd   nested=1
+```
+
+### Vagrantfile and configs
+
+There are two `Vagrantfile` to help developers.
+
+- `spec/Vagrantfile` make an environment on Ubuntu guest.
+- `spec/fedora/Vagrantfile` make an alternative environment on Fedora guest.
+
+
+## Specs
+
+To run specs, you first need to add and prepare the Vagrant box which will be used.
+
+```bash
+$ bundle exec rake box:add
+$ bundle exec rake box:prepare
+```
+
+Once box is added and prepared, you can run specs:
+
+```bash
+$ bundle exec rspec spec/vagrant-kvm/
+```
+
+When you're done, feel free to remove the box.
+
+```bash
+$ bundle exec rake box:remove
+```
+
+## Travis-CI
+
+TBD
+
+

data/Gemfile

@@ -7,4 +7,5 @@ group :development do
   # gem dependency because we expect to be installed within the
   # Vagrant environment itself using `vagrant plugin`.
   gem "vagrant", :git => "git://github.com/mitchellh/vagrant.git"
+  gem "log4r", '1.1.10'
 end

data/INSTALL.md

@@ -0,0 +1,229 @@
+# Installation
+
+## Requirements
+
+This plugin requires QEMU 1.1+.
+
+It also requires libvirt development files to complete installation with
+dependent ruby-libvirt gems.
+
+### Debian/Ubuntu requirements
+
+This plugin requires
+
+- For KVM:
+ * `qemu`, `qemu-kvm`,`libvirt-bin` packages
+ * qemu 1.1 and after
+ * libvirt 1.0 and after
+
+- For NFS:
+ * `nfs-kernel-server`,`nfs-common`,`portmap`
+
+- For Networking:
+ * `redir` `dnsmasq-base` `bridge-utils`
+
+- For `ruby-libvirt` gems installation dependency:
+ * `build-essential` `ruby2.0-dev` `libvirt-dev` `libxslt1-dev` `libxml2-dev`
+
+Some kernel version has a bug that causes a permission error on image.
+You are strongly recommended to upgrade a `linux-image` up-to-date.
+If you have some reason not to update, you should install
+`apparmor-profiles` and `apparmor-utils` and
+consult the Known Issues section in README.md.
+https://github.com/adrahon/vagrant-kvm/blob/master/README.md#known-issues
+
+You can use a backported KVM/QEMU 1.4 with Private Package Archive(PPA)
+for Ubuntu 12.04(LTS) at
+ [launchpad-ppa](https://launchpad.net/~miurahr/+archive/vagrant)
+
+### Debian/Ubuntu preparation
+
+Before starting plugin installation, you need to configure your user id.
+Access to the management layer of libvirt is controlled through membership
+to the libvirtd unix group.
+
+To enable libvirt management access for a user, add them to this group:
+
+```bash
+$ sudo usermod -G libvirtd  -a ~~usrname~~
+```
+
+### Fedora/CentOS/RedHat/openSUSE requirements
+
+- For KVM:
+  * `qemu-kvm` `libvirt` `libvirt-daemon-kvm.x86_64`
+
+- For NFS:
+ * `nfs-utils`
+
+- For Networking:
+ * `redir`
+
+- For `ruby-libvirt` gems installation dependency:
+ * `gcc` `make` `rubygem-rake` `ruby-devel` `libvirt-devel` `libxslt-devel` `libxml2-devel`
+
+### Fedora preparation
+
+Home directory permission is too conservative for Vagrant with kvm.
+Please relax your home directory permissions.
+
+```bash
+$ chmod o+x $HOME
+```
+
+To start libvirt:
+
+```bash
+$ sudo systemctl enable libvirtd
+$ sudo systemctl start libvirtd
+$ sudo systemctl enable libvirt-guests
+$ sudo systemctl start libvirt-guests
+```
+
+#### Additional information
+
+You may need to add SELinux label to vagrant standard storage-pool directory
+and box directory.
+
+```bash
+$ sudo yum install policycoreutils-python
+$ semanage fcontext -a -t virt_image_t "~/.vagrant.d/tmp/storage-pool(/.*)?"
+$ restorecon -R ~/.vagrant.d/tmp/storage-pool
+$ semanage fcontext -a -t virt_image_t "~/.vagrant.d/boxes(/.*)?"
+$ restorecon -R ~/.vagrant.d/boxes
+```
+
+Verify that this worked with
+```bash
+$ ls -Z ~/.vagrant.d/tmp/
+$ ls -Z ~/.vagrant.d/
+```
+
+Fedora uses PolicyKit to manage access to libvirt,
+an additional polkit rules file may be required.
+Following sample configure that user who is in __virt__ group
+can access libvirt in user privilege.
+
+/etc/polkit-1/rules.d/10.virt.rules
+```
+polkit.addRule(function(action, subject) {
+  polkit.log("action=" + action);
+  polkit.log("subject=" + subject);
+  var now = new Date();
+  polkit.log("now=" + now)
+  if ((action.id == "org.libvirt.unix.manage" || action.id == "org.libvirt.unix.monitor") && subject.isInGroup("virt")) {
+    return polkit.Result.YES;
+  }
+  return null;
+});
+```
+And Polkit user configuration
+
+```bash
+$ sudo groupadd virt
+$ sudo usermod -a -G virt ~~username~~
+```
+
+Then restart polkit service
+```bash
+$ systemctl restart polkit.service
+```
+
+Alternatively, you can use polkit local authority compatibility configuration
+
+```bash
+$ sudo yum install -y polkit-pkla-compat
+```
+
+/etc/polkit-1/localauthority/50-vagrant-libvirt-access.pkla:
+```
+[libvirt Management Access]
+Identity=unix-group:virt
+Action=org.libvirt.unix.manage;org.libvirt.unix.monitor
+ResultAny=yes
+ResultInactive=yes
+ResultActive=yes
+```
+
+And Polkit user configuration
+
+```bash
+$ sudo groupadd virt
+$ sudo usermod -a -G virt ~~username~~
+```
+
+Then restart polkit service
+```bash
+$ systemctl restart polkit.service
+```
+
+Consult the polkit section of [libvirt document](http://libvirt.org/auth.html#ACL_server_polkit) for details.
+Here is also a good [reference blog post](https://niranjanmr.wordpress.com/2013/03/20/auth-libvirt-using-polkit-in-fedora-18/)
+
+###CentOS6/RedHat6 preparation
+
+You may need to add SELinux label to vagrant standard storage-pool directory
+and box directory.
+
+```bash
+$ sudo yum install policycoreutils-python
+$ semanage fcontext -a -t virt_image_t "~/.vagrant.d/tmp/storage-pool(/.*)?"
+$ restorecon -R ~/.vagrant.d/tmp/storage-pool
+$ semanage fcontext -a -t virt_image_t "~/.vagrant.d/boxes(/.*)?"
+$ restorecon -R ~/.vagrant.d/boxes
+```
+
+Add polkit configuration file to allow non-root user to access libvirt.
+
+/etc/polkit-1/localauthority/50-local.d/50-libvirt-remote-access.pkla:
+```
+[libvirt Management Access]
+Identity=unix-user:username
+Action=org.libvirt.unix.manage
+ResultAny=yes
+ResultInactive=yes
+ResultActive=yes
+```
+
+Restart libvirtd
+
+```bash
+$ sudo /etc/init.d/libvirtd restart
+```
+
+
+### ArchLinux requirements
+
+This plugin requires
+
+- For KVM:
+ * `qemu-kvm`,`libvirt`
+
+- For NFS:
+  * `nfs-utils`
+
+- For Networking:
+ * `redir` `bridge-utils` `dnsmasq`
+
+- For `ruby-libvirt` gems installation dependency:
+ * `libvirt-dev`
+
+Home directory permission is too conservative for Vagrant with kvm.
+Please relax your home directory permission.
+
+```bash
+$ chmod o+x $HOME
+```
+
+To use with Vagrant, you may need to configure libvirt for non-root user to run KVM.
+Consult [ArchLinux Wiki](https://wiki.archlinux.org/index.php/Libvirt#Configuration)
+for details.
+
+
+## Install procedure
+
+As usual, you can install `vagrant-kvm` using `vagrant plugin install` command.
+```bash
+$ vagrant plugin install vagrant-kvm
+```
+

data/LICENSE

@@ -1,5 +1,6 @@
 The MIT License (MIT)
-Copyright (c) 2013 Alex Drahon
+Copyright (c) 2013,2014 Alex Drahon
+Copyright (c) 2013,2014 Hiroshi Miura
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
 

data/README.md

@@ -1,71 +1,95 @@
+[![Build Status](https://travis-ci.org/adrahon/vagrant-kvm.png)](https://travis-ci.org/adrahon/vagrant-kvm)
+
 # Vagrant KVM Provider
 
 This is a [Vagrant](http://www.vagrantup.com) 1.1+ plugin that adds a KVM
 provider to Vagrant, allowing Vagrant to control and provision KVM/QEMU VM.
 
-**NOTE:** This plugin requires Vagrant 1.1+
+## Requirements
 
-**NOTE:** This plugin requires QEMU 1.2+, it has only been tested on Fedora 18,
+This plugin requires QEMU 1.1+, it has only been tested on Fedora 18+,
 Debian Wheezy, Ubuntu 12.04(LTS) Precise and Ubuntu 13.04 Raring at the moment.
 
-**NOTE:** This plugin requires `libvirt-dev` package to be installed 
-(as in Debian/Ubuntu) or `libvirt-devel` (Fedora/openSUSE)
+This plugin requires several library and helper utils packages.
+Consult the [Requirements section in INSTALL.md](https://github.com/adrahon/vagrant-kvm/blob/master/INSTALL.md)
+
+## Recent changes
+
+Default image format is now qcow2 instead of sparsed raw image, with qcow2
+`vagrant-kvm` uses the box volume as a backing volume so that VM creation is
+a lot faster. In most cases you want to use qcow2.
 
-**NOTE** You can use a backported KVM/QEMU 1.2 with Private Package Archive(PPA)
-for Ubuntu 12.04(LTS) at https://launchpad.net/~miurahr/+archive/vagrant
+OVF boxes conversion as been removed, you should use `vagrant-mutate` instead.
 
 ## Features/Limitations
 
 * Provides the same workflow as the Vagrant VirtualBox provider.
-* Uses VirtualBox boxes almost seamlessly (see below).
 * Uses NFS for sync folders
 * Only works with 1 VM per Vagrantfile for now
-* Only works with private networking for now
-* Requires "libvirt" group membership to run vagrant (Debian/Ubuntu only)
+* Requires "libvirtd" group membership to run Vagrant (Debian/Ubuntu only)
 * Requires backporting qemu and libvirt from experimental (Debian) or raring (Ubuntu)
+* Use qcow2 backing image by default, which should make VM creation very fast
 
-## Usage
+## Known issues
 
-Install using standard Vagrant 1.1+ plugin installation methods. After
-installing, `vagrant up` and specify the `kvm` provider. An example is
-shown below.
+### Ubuntu
+Some versions of Ubuntu kernel has a bug that will cause vagrant-kvm
+to fail with a permission error on `vagrant up`. It is a kernel bug with the AppArmor security framework.
+As a workaround, please run following command to disable access control for libvirt helper.
 
-```
-$ vagrant plugin install vagrant-kvm
-...
-$ vagrant up --provider=kvm
-...
+```bash
+sudo aa-complain /usr/lib/libvirt/virt-aa-helper
 ```
 
-Of course prior to doing this, you'll need to obtain a KVM-compatible
-box file for Vagrant.
+### Fedora and Arch
+With Fedora and Arch, default home directory permissions are set to `drwx------`.
+Qemu/kvm runs as 'qemu' user by default and cannot access your home directory.
 
-## Quick Start
+To avoid this, please check and change your home directory and
+child directories permission to permit qemu user access to `~/.vagrant.d/tmp/storage-pool/`
 
-After installing the plugin (instructions above), the quickest way to get
-started is to use a VirtualBox box and change the provider manually. For
-example:
+```bash
+$ chmod go+x /home/<your account>
+```
+
+Another option is to run qemu/kvm as the root user by changing the
+configuration in libvirt.
 
+/etc/libvirt/qemu.conf
 ```
-$ vagrant box add precise32 http://files.vagrantup.com/precise32.box
-...
+user = "root"
+group = "root"
 ```
 
-The box will be installed in `~/.vagrant.d/boxes/precise32/virtualbox`, you
-need to change this to `~/.vagrant.d/boxes/precise32/kvm` and change the
-provider in `metadata.json`. For example:
+Then restart libvirtd.
 
+```bash
+$ sudo systemctl restart libvirtd
 ```
-mv ~/.vagrant.d/boxes/precise32/virtualbox ~/.vagrant.d/boxes/precise32/kvm
-cat <<EOF >~/.vagrant.d/boxes/precise32/kvm/metadata.json
-> {"provider": "kvm"}
-> EOF
+
+This may or may not be sufficient to make it work with Fedora, there are still
+some issues for some users on Fedora 20.
+
+## Usage
+
+Install using the standard Vagrant 1.1+ plugin installation command. After
+installation, use `vagrant up` and specify the `kvm` provider. An example is
+shown below.
+
+```bash
+$ vagrant plugin install vagrant-kvm
+$ vagrant up --provider=kvm
 ```
 
+Of course prior to doing this, you'll need to obtain a KVM-compatible
+box file for Vagrant. You can convert a VirtualBox base box using
+`vagrant-mutate` https://github.com/sciurus/vagrant-mutate or see the sample
+box.
+
 You will need a private network specifying an IP address in your Vagrantfile,
 the minimum Vagrantfile would then be:
 
-```
+```ruby
 Vagrant.configure("2") do |config|
   config.vm.box = "precise32"
   config.vm.network :private_network, ip: "192.168.192.10"
@@ -75,49 +99,116 @@ end
 And then run `vagrant up --provider=kvm`.
 
 If you always use kvm provider as default, please set it in your .bashrc:
-```
+
+```bash
 export VAGRANT_DEFAULT_PROVIDER=kvm
 ```
-then you can simply run `vagrant up` with kvm provider.
+then you can simply run `vagrant up` to use the kvm provider.
 
-## Box Format
+## Configuration
 
-Vagrant providers each require a custom provider-specific box format.
-This folder shows the example contents of a box for the `kvm` provider.
+There are some provider specific parameter to control VM definition.
 
-There are two box formats for the `kvm` provider:
+* `cpu_model` - cpu architecture: 'i686' or 'x86_64': default is x86_64. Note
+  that your base box should specify this.
+* `core_number` - number of cpu cores.
+* `memory_size` - memory size such as 512m, 1GiB, 100000KiB, unit is KiB if
+  unspecified.
+* `gui` - boolean for starting VM with VNC enabled.
+* `vnc_port` - The port the VNC server listens to. Default is automatic port
+assignment.
+* `vnc_autoport` - if true, KVM will automatically assign a port for VNC
+to listen to. Defaults to false, but the default vnc_port is -1, which results
+in this flag being automatically turned on by KVM.
+* `vnc_password ` - A password used to protect the VNC session.
+* `image_type` - an image format for vm disk: 'raw' or 'qcow2': default is "qcow2"
+  When choosing 'raw', vagrant-kvm always convert box image into storage-pool,
+  which consumes disk space and is a longer process. Recommendation is 'qcow2'.
+* `machine_type` - The type of machine to boot. Default is pc-1.2.
+* `network_model` - The model of the network adapter you want to use. Defaults
+to virtio. Can be set to `:default` if you want to use the KVM default setting.
+Possible values include: ne2k_isa i82551 i82557b i82559er ne2k_pci pcnet rtl8139 e1000 virtio.
+* `video_model` - The model of the video adapter. Default to cirrus. Can also be
+set to vga.
+* `image_mode` - Possible value are `clone` or `cow`, defaults to `cow`. If set
+to `clone`, the image disk will be copied rather than use the original box
+image. This is slower but allows multiple VMs to be booted at the same time.
+* `force_pause` - use `pause` for `vagrant suspend` instead of `suspend`.
+  It keeps resource online but execution is stopped.
+  When VM has a device that is not supported `hibernate`, automatically use
+  `pause` regardless of this.
 
-1. VirtualBox box - you need to change the provider to `kvm` in the
-   `metadata.json` file, the box will be converted on the fly.
-2. "Native" box - you need a box.xml file (libvirt domain format) and a raw
-   image file (you can convert a .vmdk with qemu-img)
 
-To turn this into a native box, you need to create a vagrant image and
-make it sparse.
-You need ```libguestfs-tools``` package 
-in Debian/Ubuntu/Mint, Fedora15 and after, or CentOS/RHEL6.
+## Comparison with [Vagrant-libvirt](https://github.com/pradels/vagrant-libvirt)
 
-```
-$ env TMPDIR=/tmp virt-sparsify box-disk1-orig.img box-disk1.img
-```
+Vagrant-kvm is a KVM/Qemu provider for single local host.
+Vagrant-kvm is simple, local host only, qemu/kvm only provider that is
+intended as an alternative to VirtualBox while keeping the same workflow.
 
-Please keep enough disk space for TMPDIR!
-To make box with keeping sparse, don't forget -S in tar option:
+Vagrant-libvirt is a libvirt provider to control machines via the libvirt toolkit.
+Vagrant-libvirt covers a lot more libvirt options, local and remote hosts and multiple hypervisors,
+such as Xen, LXC and KVM/qemu.
 
-```
-$ tar cvSzf kvm.box ./metadata.json ./Vagrantfile ./box.xml ./box-disk1.img
-```
+In early 2014, Varant-libvirt only support kvm/qemu in local host, there is no big feature difference.
 
-For CentOS/RHEL5, there is a package in EPEL5. 
-For Gentoo, you can use ```emerge libguestfs```.
+Here are a few difference:
 
-You need a base MAC address and a private network like in the example.
+### 1. Travis CI and quality assurance
 
+Vagrant-kvm tests every pull request and repository with Travis-CI;
+https://travis-ci.org/adrahon/vagrant-kvm/
+Vagrant-libvirt does not.
 
-## Configuration
+### 2. Copy-on-write
 
-There are some provider specific parameter to control VM definition.
+Vagrant-kvm by default uses the qcow2 format
+and qcow2 disk image backing to create a new volume
+from the box disk.
+This makes creating a new vm very fast, with some performance penalties.
+You can change this through configuration to clone(copy) disk image to pool instead.
+This will make new vm creation slower, but give you better disk performance.
+You can also configure vagrant-kvm to use raw images for an additional
+performance gain.
 
-* `gui` - boolean for starting VM with VNC enabled.
-* `image_type` - an image format for vm disk: 'raw' or 'qcow2'
+Vagrant-libvirt use qcow2 as disk image.
+
+### 3. VNC port/password
+
+Vagrant-kvm allows you to configure how to connect with VNC, which provides virtual guest desktop.
+Vagrant-libvirt is not.
+
+### 4. Synced folder
+
+Vagrant-kvm can provide synced folder with NFS only.
+We plan to provide virtfs(p9share) to allow sharing local folders
+without root privilege.
+
+Vagrant-libvirt provide synced folder with Rsync and NFS.
+They also plan to support virtfs in future.
+
+It is neccesary to fix several bugs in libvirt/qemu to enable
+virtfs feature in both providers.
+
+### 5. Snapshots via sahara
+
+Vagrant-kvm plan to support snapshot via sahara.
+We have already proposed to sahara project to add support
+and are waiting for review.
+https://github.com/jedi4ever/sahara/pull/32
+
+Vagrant-libvirt is supported by sahara.
+
+### 6. Use boxes from other Vagrant providers via vagrant-mutate
+
+Both are supported by vagrant-mutate as convert target
+
+### 7. Architecture
+
+Vagrant-kvm control kvm/qemu via ruby-libvirt, libvirt and qemu.
+
+Vagrant-libvirt control machines via fog,
+a cloud abstraction library in ruby,
+that is also used by vagrant-aws.
+A fog library control virtual machines on supported platforms and provide
+control of qemu/kvm machines through ruby-libvirt and libvirt.