Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35000 - [libvirt] Libvirt ships with broken qemu.conf
Attached to Project:
Community Packages
Opened by Evan Callicoat (Apsu) - Saturday, 27 April 2013, 22:38 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 29 April 2013, 11:34 GMT
Opened by Evan Callicoat (Apsu) - Saturday, 27 April 2013, 22:38 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 29 April 2013, 11:34 GMT
|
DetailsWhen using libvirt with KVM, libvirt is unable to make a connction to qemu:///system, due to insufficient permissions.
The qemu.conf file in /etc/libvirt which ships with the libvirt package has no group ID specified, which causes the qemu-system-* process(es) to be spawned as nobody:nobody. This prevents libvirt from connecting through qemu:///system as the process then doesn't have access to /dev/kvm, which is root:kvm with 0660 permissions. The simple solution is to add a line to the qemu.conf, as follows: group = "kvm" This issue effectively prevents libvirt from being functional with a KVM backend out of the box. |
This task depends upon