Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #721081 +++
SELinux is preventing /usr/bin/virsh from using the 'setsched' accesses on a process.
***** Plugin catchall (100. confidence) suggests ***************************
If you believe that virsh should be allowed setsched access on processes labeled virsh_t by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep virsh /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
Additional Information:
Source Context system_u:system_r:virsh_t:s0
Target Context system_u:system_r:virsh_t:s0
Target Objects Unknown [ process ]
Source virsh
Source Path /usr/bin/virsh
Port <Sconosciuto>
Host (removed)
Source RPM Packages libvirt-client-0.8.8-4.fc15
Target RPM Packages
Policy RPM selinux-policy-3.9.16-32.fc15
Selinux Enabled True
Policy Type targeted
Enforcing Mode Enforcing
Host Name (removed)
Platform Linux (removed)
2.6.38.8-32.fc15.x86_64 #1 SMP Mon Jun 13 19:49:05
UTC 2011 x86_64 x86_64
Alert Count 1
First Seen mar 12 lug 2011 04:10:05 CEST
Last Seen mar 12 lug 2011 04:10:05 CEST
Local ID 5d1303e4-7348-4117-906d-c3b4f98ec162
Raw Audit Messages
type=AVC msg=audit(1310436605.76:256): avc: denied { setsched } for pid=18640 comm="virsh" scontext=system_u:system_r:virsh_t:s0 tcontext=system_u:system_r:virsh_t:s0 tclass=process
type=SYSCALL msg=audit(1310436605.76:256): arch=x86_64 syscall=setpriority success=no exit=EACCES a0=0 a1=0 a2=0 a3=7f78e81df9d0 items=0 ppid=18598 pid=18640 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=virsh exe=/usr/bin/virsh subj=system_u:system_r:virsh_t:s0 key=(null)
Hash: virsh,virsh_t,virsh_t,process,setsched
audit2allow
#============= virsh_t ==============
allow virsh_t self:process setsched;
audit2allow -R
#============= virsh_t ==============
allow virsh_t self:process setsched;
--- Additional comment from dwalsh on 2011-07-13 13:51:46 EDT ---
Seems ok.
Need to back port this to RHEL6.