Red Hat Bugzilla – Bug 448060
host of SELinux AVC denials on starting kvm virtual machine
Last modified: 2018-04-11 05:33:08 EDT
Description of problem:
Tried running virsh create as normal user and got a host of AVC denials (see
attached). The only difference from the plain system is that (in order to get to
the /etc/libvirtd) I have run
chgrp -R virt /etc/libvirt
chmod g+rX /etc/libvirt
Version-Release number of selected component (if applicable):
[matej@viklef ~]$ rpm -q libvirt PolicyKit selinux-policy-targeted kvm kernel
[matej@viklef ~]$ uname -a
Linux viklef 18.104.22.168-26.fc9.i686 #1 SMP Mon May 19 19:49:30 EDT 2008 i686 i686
Steps to Reproduce:
Created attachment 306462 [details]
output of /sbin/ausearch -ts 10:00 -m AVC
I don't think this can be fixed in libvirt. It looks more like some rules
are needed in SE-Linux policies to allow access from libvirtd to the networking
commands. So reassigning,
This shows virtsh running lockit? Which I guess could allow a user to influence
the SELinux settings as well as the fire wall settings? Why is libvirt doing this?
Most of the rest of these are fixed in
Fixed in selinux-policy-3.3.1-60.fc9
Fixed in selinux-policy-3.3.1-74.fc9.noarch
Decided to make libvirtd an unconfined domain, since it can now load kernel
modules and set iptables rules.
Oh well, probably the best what we can expect. Thanks a lot for fixing this.
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here: