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.
DescriptionMichal Sekletar
2020-03-31 09:14:33 UTC
This bug was initially created as a copy of Bug #1787038
I am copying this bug because: systemd in RHEL-8.2 is introducing support for cpuset cgroup controller on cgroup v2 and SELinux is preventing systemd from managing cpusets.
Description of problem:
Everytime I tried to start a VM either using virsh start <domain> or using VMM gui tool.
Also working with podman starting containers using local directories for volume binds.
SELinux is preventing systemd from using the 'setsched' accesses on a process.
***** Plugin catchall (100. confidence) suggests **************************
If you believe that systemd should be allowed setsched access on processes labeled virtd_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:
# ausearch -c 'systemd' --raw | audit2allow -M my-systemd
# semodule -X 300 -i my-systemd.pp
Additional Information:
Source Context system_u:system_r:init_t:s0
Target Context system_u:system_r:virtd_t:s0-s0:c0.c1023
Target Objects Unknown [ process ]
Source systemd
Source Path systemd
Port <Unknown>
Host (removed)
Source RPM Packages
Target RPM Packages
Policy RPM <Unknown>
Selinux Enabled True
Policy Type targeted
Enforcing Mode Enforcing
Host Name (removed)
Platform Linux (removed) 5.3.16-300.fc31.x86_64 #1 SMP Fri
Dec 13 17:59:04 UTC 2019 x86_64 x86_64
Alert Count 3
First Seen 2019-12-30 14:53:23 CET
Last Seen 2019-12-30 15:05:45 CET
Local ID cf2a5796-2ea6-4f7b-be19-fd6f2336e002
Raw Audit Messages
type=AVC msg=audit(1577714745.43:1142): avc: denied { setsched } for pid=1 comm="systemd" scontext=system_u:system_r:init_t:s0 tcontext=system_u:system_r:virtd_t:s0-s0:c0.c1023 tclass=process permissive=0
Hash: systemd,init_t,virtd_t,process,setsched
Additional info:
component: selinux-policy
reporter: libreport-2.11.3
hashmarkername: setroubleshoot
kernel: 5.3.16-300.fc31.x86_64
type: libreport
Potential duplicate: bug 1777422
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (selinux-policy bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:4528