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.

Description of problem:
Libvirt can create network connection between two guests using unix_stream_socket but it is denied by selinux. Please add:

allow svirt_t svirt_t : unix_stream_socket { connectto } ;


Version-Release number of selected component (if applicable):
selinux-policy-3.13.1-7.el7.noarch

(In reply to Pavel Hrdina from comment #0)
> Description of problem:
> Libvirt can create network connection between two guests using
> unix_stream_socket but it is denied by selinux. Please add:
> 
> allow svirt_t svirt_t : unix_stream_socket { connectto } ;
> 

This will only allow one VM connect to another. But VMs can be configured to connect to something different, e.g. a tcp console. That would imply allowing svirt_t to connect to any other type. But saying that aloud looks like too wide policy, right?

commit 6a877f34ad53909a89b7780b28e584b159e894a2
Author: Miroslav Grepl <mgrepl>
Date:   Thu Nov 6 18:32:05 2014 +0100

    - Allow guest to connect to libvirt using unix_stream_socket.

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://rhn.redhat.com/errata/RHBA-2015-0458.html