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
- 1 Installing
- 2 Configuration
- 3 Usage
- 4 Remote access to libvirt
- 5 Bridged Networking
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 AUR in the repositories currently disables Xen with the
--with-out xen 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 AUR installed.
The alternative XenAPI driver is lacking a package at the moment? (2010-05-23, friesoft)
Seems that you have to start dbus and avahi-daemon before starting libvirtd.
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
Try to re-login if it does not work right away.
Alternatively, you can grant only the monitoring rights with
When logging in via SSH, you will need to make sure ConsoleKit is used. Place the following in
Unix File-based Permissions
If you wish to use Unix file-based permissions to allow some non-root users to use
libvirt, you can modify the configuration files.
First, you will need to create the
libvirt group and add any users you want to have access to libvirt to that group. See Users and Groups for more information.
# 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
# patch -Np1 -i "$srcdir"/unixperms.patch || return 1
Alternatively, you can make the changes to your permissions and configuration files by hand. Uncomment the following lines in
/etc/libvirt/libvirtd.conf (they are not all in the same location in the file):
Enable KVM acceleration for QEMU
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
kvm-intel kernel module depending on your CPU.
# modprobe kvm-amd
Usually you would also add it to the
MODULES= line in
If KVM is not working, you will find the following message in your
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
.iso file. Copy it to the
/var/lib/libvirt/images/ directory (alternatively, you can create a new storage pool directory in virt-manager and copy it there).
virt-manager, 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
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)
It is also necessary to start the server in listening mode by editing
The SSH.package is needed for remote management over
To connect to the remote system using
$ 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
General examples are given in
Unofficial example usingand :
#! /usr/bin/env python2 # -*- coding: utf-8 -*- import socket import sys import libvirt if (__name__ == "__main__"): conn = libvirt.open("qemu+ssh://xxx/system") print "Trying to find node on xxx" domains = conn.listDomainsID() for domainID in domains: domConnect = conn.lookupByID(domainID) if domConnect.name() == 'xxx-node': print "Found shared node on xxx with ID " + str(domainID) domServ = domConnect break
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.
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):
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' /> </interface> [...]
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
<model type='virtio' />:
[...] <interface type='bridge'> <source bridge='br0'/> <mac address='24:42:53:21:52:49'/> </interface> [...]