What is the reasoning behind disabling Xen integration? I'm tempted to open a bug for the missing Xen integration, but I assume there is a reason it is excluded.
- I'm assuming that Xen integration is disabled because AUR is not in the official repositories. Even if an Arch user manages Xen VMs on remote systems (I'm assuming the remote systems are not running Arch), enabling Xen support in Arch's package isn't going to help because when you connect to a remote VM host, you are connecting to the remote host's libvirt daemon, so only the remote host would need libvirt to support Xen. You could open an issue on the bug tracker requesting that Xen support be enabled, but I'm guessing it won't happen.
- -- Jstjohn (talk) 03:25, 5 December 2013 (UTC)
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
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='http://libvirt.org/schemas/domain/qemu/1.0'> ... <qemu:commandline> <qemu:arg value='-machine'/> <qemu:arg value='accel=kvm'/> <qemu:arg value='kernel_irqchip=on' /> </qemu:commandline> </domain>
I don't know if there is some specific field in libvirt XML, but this works for me.
Added chip level IRQs to the argument list of Vimes656 recommendation.
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'
sudo pacman -S vte290
and change the following line in /usr/share/virt-manager/virtManager/serialcon.py
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.