From ArchWiki
Jump to navigation Jump to search

libvirt-guests and systemd

libvirt-guests does not work with systemd. At least not without modification to the scripts. To enable a guest to auto-start you can either check the "autostart" box in virt-manager, enable autostart through virsh or you can manually create a symlink in the libvirt auto-start directory.

To automatically start a guest named www that runs in qemu

ln -s /etc/libvirt/qemu/www.xml /etc/libvirt/qemu/autostart/www.xml

--En0 (talk) 14:35, 10 December 2012 (UTC)

The discussion is outdated, close. -- Blackteahamburger (talk) 09:54, 24 June 2020 (UTC)

KVM acceleration after removing qemu-kvm package

In order to have KVM acceleration after the removal of qemu-kvm I had to edit the config of my virtual machines like this:

<domain type='qemu' xmlns:qemu=''>
    <qemu:arg value='-machine'/>
    <qemu:arg value='accel=kvm'/>
    <qemu:arg value='kernel_irqchip=on' />

I don't know if there is some specific field in libvirt XML, but this works for me.

--Vimes656 (talk) 13:16, 7 March 2013 (UTC)Vimes656

Chip-level IRQs

Added chip level IRQs to the argument list of Vimes656 recommendation.

--En0 (talk) 15:49, 7 March 2013 (UTC)

kvm group

About the disput of using or not the kvm group, the discussion which lead to adding this group in the depreceated group list is there; deleted from the talk page of KVM article. Bricewge (talk) 16:26, 18 September 2014 (UTC)

Errors and possible fixes

If you get the following error(s) when creating a new virtual machine using virt-manager:

summary=Error launching details: 'Terminal' object has no attribute 'set_visible_bell'
details=Error launching details: 'Terminal' object has no attribute 'set_visible_bell'

install extra/vte290

sudo pacman -S vte290

and change the following line in /usr/share/virt-manager/virtManager/


from gi.repository import Vte


#from gi.repository import Vte
import gi
gi.require_version('Vte', '2.90')
from gi.repository import Vte

to explicitely use a vte 290 terminal

Trouble shooting when configuring network

After following the instructions configuring a libvirt environment, if one provides the argument --network bridge=xxx to
virt-install, then an error may occur:

ERROR    internal error: /usr/lib/qemu/qemu-bridge-helper --br=xxx --fd=xx: \
failed to communicate with bridge helper: Transport endpoint is not connected

stderr=failed to parse default acl file `/etc/qemu/bridge.conf'

I would like to add a note section which describes the solution to this error, which is to create a file /etc/qemu/bridge.conf with proper settings.

If you are fine with this idea, I will add it soon. --NonerKao (talk) 06:28, 22 June 2016 (UTC)

Where is '/usr/share/libosinfo/db/oses/os.xml'?

At Libvirt#Create_a_new_domain_using_virt-install Tips. I have a kvm+qrmu+libvirt+virt-manager fresh install, but I can't find that file. I tried pacman -Ql libosinfo, and pkgfile, but didn't help. Is there something wrong? Or that file has been removed? Should to be removed?

Edit:I mean, even no '/usr/share/libosinfo/ directory.Kurobac (talk) 21:11, 9 July 2018 (UTC)

This seems to be a valid concern. Both pacman -Ql libosinfo and pacman -Fs libosinfo fail to yield any results for me.
Ichimonji10 (talk) 02:41, 21 October 2019 (UTC)


The article says to install bridge-utils but according to (via

"Note: the bridge-utils package is deprecated, instead use the bridge command from iproute2 package."

Beepboo (talk) 08:45, 12 March 2020 (UTC)