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.

Bug 670258

Summary: Miscellaneous selinux problems running libguestfs in RHEL 6.1
Product: Red Hat Enterprise Linux 6 Reporter: Richard W.M. Jones <rjones>
Component: selinux-policyAssignee: Daniel Walsh <dwalsh>
Status: CLOSED NOTABUG QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: low    
Version: 6.1CC: dwalsh
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-26 21:37:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Extract from audit.log none

Description Richard W.M. Jones 2011-01-17 17:18:12 UTC
Created attachment 473898 [details]
Extract from audit.log

Description of problem:

The attached audit.log is an extract from running the
SELinux in permissive mode whilst running the command
as NON-root:

guestfish -a win2003.iso --ro -m /dev/sda

Version-Release number of selected component (if applicable):

libguestfs-1.7.17-9.el6.x86_64
selinux-policy-targeted-3.7.19-54.el6_0.3.noarch
selinux-policy-3.7.19-54.el6_0.3.noarch

Comment 1 Richard W.M. Jones 2011-01-17 17:21:10 UTC
audit2allow is suggesting:

#============= qemu_t ==============
allow qemu_t boot_t:file { read getattr open };
allow qemu_t unconfined_t:unix_stream_socket connectto;
allow qemu_t user_tmp_t:file { read ioctl open };
allow qemu_t user_tmp_t:sock_file write;

Comment 2 Richard W.M. Jones 2011-01-17 17:22:58 UTC
libguestfs works by running the following qemu-kvm command.
The command is generated and may be slightly different
each time.

/usr/libexec/qemu-kvm \
    -drive file=en_win_srv_2003_r2_enterprise_with_sp2_cd1_X13-05460.iso,snapshot=on,if=virtio \
    -nodefconfig \
    -enable-kvm \
    -nodefaults \
    -nographic \
    -m 500 \
    -no-reboot \
    -device virtio-serial \
    -serial stdio \
    -chardev socket,path=/tmp/libguestfsxJgTAK/sock,id=channel0 \
    -device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 \
    -kernel /tmp/.guestfs-500/kernel.5197 \
    -initrd /tmp/.guestfs-500/initrd.5197 \
    -append 'panic=1 console=ttyS0 udevtimeout=300 noapic acpi=off printk.time=1 cgroup_disable=memory selinux=0 guestfs_verbose=1 TERM=xterm ' \
    -drive file=/tmp/.guestfs-500/root.5197,snapshot=on,if=virtio,cache=writeback

Comment 3 Daniel Walsh 2011-01-17 19:08:50 UTC
I think it is probably better to turn the transition off to a confined qemu.

# setsebool -P allow_unconfined_qemu_transition 0

We really do not use this confinement much since we have moved to svirt confinement.

Comment 4 Richard W.M. Jones 2011-01-17 19:56:11 UTC
(In reply to comment #3)
> I think it is probably better to turn the transition off to a confined qemu.
> 
> # setsebool -P allow_unconfined_qemu_transition 0
> 
> We really do not use this confinement much since we have moved to svirt
> confinement.

Is this a suggestion that you want me to try out?

I think on this system I changed this setting.  Currently
it is set to:

$ getsebool allow_unconfined_qemu_transition
allow_unconfined_qemu_transition --> on

Comment 5 Daniel Walsh 2011-01-17 20:47:09 UTC
Yes I want you to turn it off.  Therefore qemu will run under the unconfined domain.

Comment 6 Richard W.M. Jones 2011-01-17 20:55:28 UTC
That fixes the problem.  However I'm fairly sure I turned
this boolean on before for a reason, although I can't recall
what it was now.  I guess I'll wait to see if anything breaks.