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.
(In reply to Milos Malik from comment #3)
> I wonder why is the deleted file labeled svirt_image_t. Is it really a
> virtual machine image?
>
> *
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/
> html-single/virtualization_security_guide/#sect-
> Virtualization_Security_Guide-sVirt-Labels
Sorry, I'm not sure.
Hi yafu,
Could you help answer this question?
This file is created by qemu-kvm (qemu will create a tmp file then mmap memory and then delete this file in this case) and the directory /dev/hugepages2M/libvirt/qemu/1-avocado-vt-vm1/ is created by libvirt and libvirt change this dir context to system_u:object_r:svirt_image_t:s0:cxxx,cxxx , that is why this file labeled svirt_image_t.
I checked this issue have already been fixed in Fedora (see bug 1514538) and here is the result of sesearch in F28:
# sesearch -A -s svirt_t -t svirt_image_t
allow svirt_t svirt_image_t:file map;
...
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:3111
Description of problem: SELinux is preventing /usr/libexec/qemu-kvm from map access Additional Information: Source Context system_u:system_r:svirt_t:s0:c296,c387 Target Context system_u:object_r:svirt_image_t:s0 Target Objects Please check message Source qemu-kvm Source Path /usr/libexec/qemu-kvm Port <Unknown> Host host.example.com Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-204.el7.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name host.example.com Platform Linux host.example.com kernel-3.10.0-897.el7.x86_64 Alert Count 1 First Seen <Unknown> Last Seen 2018-06-19 03:00:00 EDT Local ID <Unknown> Raw Audit Messages type=AVC msg=audit(1529373654.545:13947): avc: denied { map } for pid=20718 comm="qemu-kvm" path=2F6465762F687567657061676573324D2F6C6962766972742F71656D752F312D61766F6361646F2D76742D766D312F71656D755F6261636B5F6D656D2E5F6F626A656374735F72616D2D6E6F6465302E34315147524F202864656C6574656429 dev="hugetlbfs" ino=452846 scontext=system_u:system_r:svirt_t:s0:c296,c387 tcontext=system_u:object_r:svirt_image_t:s0 tclass=file permissive=0 Hash: qemu-kvm,svirt_t,svirt_image_t,file,map