From ArchWiki
Revision as of 05:54, 26 October 2011 by Jstjohn (talk | contribs) (Unix File-based Permissions: forgot to remove a trailing "}}")
Jump to: navigation, search

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.

Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어

External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

Template:Article summary start Template:Article summary text Template:Article summary heading Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary wiki Template:Article summary end

libvirt is a virtualization API and a daemon for managing virtual machines (VMs) -- remote or locally, using multiple virtualization backends (QEMU/KVM, VirtualBox, Xen, etc).


For servers you need the following packages from the official Arch Linux repositories:

For GUI management tools, you also need all of the following from the official Arch Linux repositories:

Building libvirt for Xen

The PKGBUILD for Template:Package AUR in the repositories currently disables Xen with the Template:Codeline flag during the make process. If you want to use libvirt for managing Xen, you will need to grab the whole fileset to re-enable it. Furthermore, you need to make sure you have Template:Package AUR installed.

The alternative XenAPI driver is lacking a package at the moment? (2010-05-23, friesoft)


Run daemon

Start the libvirtd daemon and add Template:Codeline to your DAEMONS array so it starts automatically on boot.

Seems that you have to start dbus and avahi-daemon before starting libvirtd.

Note: The Avahi daemon is used for local discovery of libvirt hosts via multicast-DNS.

PolicyKit authentication

To allow yourself to manage VMs as a non-root user, run this on the server:

# polkit-auth --user $USERNAME --grant org.libvirt.unix.manage
Note: As Template:Codeline is deprecated, you have to create the following file.


Try to re-login if it does not work right away.

Alternatively, you can grant only the monitoring rights with Template:Codeline

When logging in via SSH, you will need to make sure ConsoleKit is used. Place the following in Template:Filename:


Unix File-based Permissions

Note: This is an alternative to Polkit authentication.

If you wish to use Unix file-based permissions to allow some non-root users to use Template:Codeline, you can modify the config files.

First, you will need to create the Template:Codeline group and add any users you want to have access to libvirt to that group.

# groupadd libvirt
# gpasswd -a [username] libvirt

Any users that are currently logged in will need to log out and back in to update their groups. Alternatively, the user can use the following command in the shell they will be launching libvirt from to update the group:

$ newgrp libvirt

Then you can either enable permissions-based access by uncommenting the following line in the PKGBUILD for libvirt before running Template:Codeline:

# patch -Np1 -i "$srcdir"/unixperms.patch || return 1

Alternatively, you can make the changes to your permissions and config files by hand. Uncomment the following lines in Template:Filename (they are not all in the same location in the file):


Note: You may also wish to change unix_sock_ro_perms from "0777" to "0770" to disallow read-only access to people who are not members of the libvirt group.

Enable KVM acceleration for QEMU

Note: KVM will conflict with VirtualBox. You cannot use KVM and VirtualBox at the same time.

Running virtual machines with the usual QEMU emulation (i.e. without KVM)), will be painfully slow. You definitely want to enable KVM support if your CPU supports it. To find out, run the following command:

grep -E "(vmx|svm)" --color=always /proc/cpuinfo

If that command generates output, then your CPU supports hardware acceleration via KVM; if that command does not generate output, then you cannot use KVM.

To enable KVM, you need to load the Template:Codeline or Template:Codeline kernel module depending on your CPU.

# modprobe kvm-amd

Usually you would also add it to the Template:Codeline line in Template:Filename Template:File

If KVM is not working, you will find the following message in your Template:Filename: Template:File

More info is available from the official KVM FAQ


Installing a new VM

To create a new VM, you need some sort of installation media, which is usually a standard Template:Codeline file. Copy it to the Template:Filename directory (alternatively, you can create a new storage pool directory in virt-manager and copy it there).

Note: SELinux requires that virtual machines be stored in Template:Filename by default. If you use SELinux and are having issues with virtual machines, ensure that your VMs are in that directory or ensure that you have added the correct labeling to the non-default directory that you used.

Then run Template:Codeline, connect to the server, right click on the connection and choose New. Choose a name, and select Local install media. Just continue with the wizard.

On the 4th step, you may want to uncheck Allocate entire disk now -- this way you will save space when your VM is not using all of its disk. However, this can cause increased fragmentation of the disk, and you must pay attention to the total available disk space on the VM host because it is much easier to over-allocate disk space to VMs.

On the 5th step, open Advanced options and make sure that Virt Type is set to kvm. If the kvm choice is not available, see section Enable KVM acceleration for QEMU above.

Creating a storage pool in virt-manager

First, connect to an existing server. Once you are there, right click and choose Details. Go to Storage and press the + icon at the lower left. Then just follow the wizard. :)

Using VirtualBox with virt-manager

Note: VirtualBox support in libvirt is not quite stable yet and may cause your libvirtd to crash. Usually this is harmless and everything will be back once you restart the daemon.

virt-manager does not let you to add any VirtualBox connections from the GUI. However, you can launch it from the command line:

virt-manager -c vbox:///system

Or if you want to manage a remote system over SSH:

virt-manager -c vbox+ssh://username@host/system

Remote access to libvirt

Using unencrypted TCP/IP socket (most simple, least secure)

Warning: This should only be used for testing or use over a secure, private, and trusted network.

Edit Template:Filename: Template:File

Warning: We do not enable SASL here, so all TCP traffic is cleartext! For real world use, always enable SASL.

It is also necessary to start the server in listening mode by editing Template:Filename Template:File

Using SSH

The openbsd-netcat package is needed for remote management over SSH.

To connect to the remote system using Template:Codeline:

$ virsh -c qemu+ssh://username@host/IP address/system

If something goes wrong, you can get some logs using:

$ LIBVIRT_DEBUG=1 virsh -c qemu+ssh://username@host/IP address/system

To display the graphical console for a virtual machine:

$ virt-viewer --connect qemu+ssh://username@host/IP address/system myvirtualmachine

To display the virtual machine desktop management tool:

$ virt-manager -c qemu+ssh://username@host/IP address/system

Using Python

The libvirt package comes with a python2 API in Template:Filename

General examples are given in Template:Filename

Unofficial example using qemu and openssh:

#! /usr/bin/env python2
# -*- coding: utf-8 -*-
import socket
import sys
import libvirt
if (__name__ == "__main__"):
   conn ="qemu+ssh://xxx/system")
   print "Trying to find node on xxx"
   domains = conn.listDomainsID()
   for domainID in domains:
       domConnect = conn.lookupByID(domainID)
       if == 'xxx-node':
           print "Found shared node on xxx with ID " + str(domainID)
           domServ = domConnect

Bridged Networking

To use physical Ethernet from your virtual machines, you have to create a bridge between your physical Ethernet device (here eth0) and the virtual Ethernet device the VM is using.

Host configuration

libvirt creates the bridge virbr0 for NAT networking, so use another name such as br0 or virbr1. You have to create a new Netcfg Profile to configure the bridge, for example (with DHCP configuration):


Tip: It is recommended that you enable Spanning Tree Protocol (STP) on the virtual bridge (e.g. br0) that you create to avoid any potential bridging loops. You can automatically enable STP on the bridge at start-up by appending Template:Codeline to Template:Filename.

Guest configuration

Now we have to activate the bridge interface in our VMs. If have a recent Linux machine, you can use this code in the .xml file:

 <interface type='bridge'>
   <source bridge='br0'/>
   <mac address='24:42:53:21:52:49'/>
   <model type='virtio' />

This code activates a virtio device on the machine so, in Windows you will have to install an additional driver (you can find it here Windows KVM VirtIO drivers) or remove the line Template:Codeline:

 <interface type='bridge'>
   <source bridge='br0'/>
   <mac address='24:42:53:21:52:49'/>