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.
DescriptionJean-Tsung Hsiao
2017-08-31 14:41:28 UTC
Description of problem: The qemu-kvm process got an AVC on starting a guest in OVS-dpdk environment
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.9.0-20.el7a.x86_64
openvswitch-selinux-policy-2.8.90-2.fc25.noarch
kernel-3.10.0-693.el7.x86_64
openvswitch-2.8.0-0.1.20170810git3631ed2.el7fdb.x86_64
How reproducible:reproducible
Steps to Reproduce:
0. Set selinux to permissive
1. Create an OVS 2.8.0 OVS-dpdk bridge with vhostusers
2. Start a guest
3. Should a audit message like:
type=AVC msg=audit(1504190214.374:3823): avc: denied { connectto } for pid=8699 comm="qemu-kvm" path="/run/openvswitch/vhost0" scontext=system_u:system_r:svirt_t:s0:c238,c545 tcontext=system_u:system_r:openvswitch_t:s0 tclass=unix_stream_socket
Actual results:
The qemu-kvm process got an AVC.
Expected results:
The qemu-kvm process should not get an AVC.
Additional info:
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, 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-2018:0763
Description of problem: The qemu-kvm process got an AVC on starting a guest in OVS-dpdk environment Version-Release number of selected component (if applicable): qemu-kvm-rhev-2.9.0-20.el7a.x86_64 openvswitch-selinux-policy-2.8.90-2.fc25.noarch kernel-3.10.0-693.el7.x86_64 openvswitch-2.8.0-0.1.20170810git3631ed2.el7fdb.x86_64 How reproducible:reproducible Steps to Reproduce: 0. Set selinux to permissive 1. Create an OVS 2.8.0 OVS-dpdk bridge with vhostusers 2. Start a guest 3. Should a audit message like: type=AVC msg=audit(1504190214.374:3823): avc: denied { connectto } for pid=8699 comm="qemu-kvm" path="/run/openvswitch/vhost0" scontext=system_u:system_r:svirt_t:s0:c238,c545 tcontext=system_u:system_r:openvswitch_t:s0 tclass=unix_stream_socket Actual results: The qemu-kvm process got an AVC. Expected results: The qemu-kvm process should not get an AVC. Additional info: