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 1102611 - The running guest will disappear while change the security_driver from "none" to "selinux"
Summary: The running guest will disappear while change the security_driver from "none"...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Ján Tomko
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1102612
TreeView+ depends on / blocked
 
Reported: 2014-05-29 09:50 UTC by zhenfeng wang
Modified: 2015-03-05 07:36 UTC (History)
7 users (show)

Fixed In Version: libvirt-1.2.7-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1102612 (view as bug list)
Environment:
Last Closed: 2015-03-05 07:36:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1105939 0 medium CLOSED Fail to start guest while disable the default security labeling 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2015:0323 0 normal SHIPPED_LIVE Low: libvirt security, bug fix, and enhancement update 2015-03-05 12:10:54 UTC

Internal Links: 1105939

Description zhenfeng wang 2014-05-29 09:50:08 UTC 
Description of problem:
The running guest will disappear while change the security_driver from "none" to "selinux"
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-1.5.3-60.el7ev_0.2.x86_64
libvirt-1.1.1-29.el7.x86_64
kernel-3.10.0-123.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Set security_driver=none in /etc/libvirt/qemu.conf
 security_driver = "none"
 #service libvirtd restart

2.Start a guest in the host
#virsh start rhel7
# virsh list
 Id    Name                           State
----------------------------------------------------
 1     rhel7                         running

3.Check the selinux label of the guest
# ps -efZ|grep rhel7
system_u:system_r:virtd_t:s0-s0:c0.c1023 qemu 9213 1 47 15:33 ?        00:00:11 /usr/libexec/qemu-kvm -name rhel7

# ll /var/lib/libvirt/images/rhel7.img -Z
-rw-------. qemu qemu system_u:object_r:virt_image_t:s0 /var/lib/libvirt/images/rhel7.img

4.Change the security_driver="selinux" in /etc/libvirt/qemu.conf
   security_driver = "selinux"
  #service libvirtd restart

5.Check the guest's status, found the guest disappear after restart the libvirtd service
# virsh list --all
 Id    Name                           State
----------------------------------------------------

#ps aux|grep rhel7

6.Check the libvirt log, find the following error
014-05-29 07:36:08.136+0000: 9554: info : libvirt version: 1.1.1, package: 29.el7 (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2014-03-24-06:10:00, x86-021.build.eng.bos.redhat.com)
2014-05-29 07:36:08.136+0000: 9554: error : qemuConnectMonitor:1378 : Failed to set security context for monitor for rhel7

7.Test the upper steps in rhel6.6, met the same error with the rhel7, however the guest in rhel6 won't disappear, it
just became "shutoff" status after restart the libvirtd service

8.It works well in rhel6.5

Actual results:
The guest will disappear while change the security_driver from "none" to "selinux"

Expected results:
The guest should keep in running status
 
Additional info:
Comment 2 Ján Tomko 2014-06-10 08:20:44 UTC 
Fixed upstream by:
commit f9bf63e673c11cd189748c29b6ea7d2cf19c8da7
Author:     Ján Tomko <jtomko>
AuthorDate: 2014-06-09 16:23:52 +0200
Commit:     Ján Tomko <jtomko>
CommitDate: 2014-06-10 10:18:24 +0200

    SELinux: don't fail silently when no label is present
    
    This fixes startup of a domain with:
    <seclabel type='none' model='dac'/>
    on a host with selinux and dac drivers and
    security_default_confined = 0
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1105939
    https://bugzilla.redhat.com/show_bug.cgi?id=1102611

git describe: v1.2.5-81-gf9bf63e
Comment 4 zhengqin 2014-08-21 07:39:24 UTC 
I could reproduce it with libvirt-1.1.1-29.el7.x86_64 as following steps:


1.Set security_driver=none in /etc/libvirt/qemu.conf
 security_driver = "none"
 #service libvirtd restart

2.Start a guest in the host
#virsh start rhel6u5
# virsh list
 Id    Name                           State
----------------------------------------------------
 1     rhel6u5                         running

3.Check the selinux label of the guest
# ps -efZ|grep rhel6u5
system_u:system_r:virtd_t:s0-s0:c0.c1023 qemu 5130 1 73 03:34 ?        00:00:01 /usr/libexec/qemu-kvm -name rhel6u5

# ll -Z /var/lib/libvirt/images/rhel6u5.img
-rw-------. qemu qemu system_u:object_r:virt_image_t:s0 /var/lib/libvirt/images/rhel6u5.img

4.Change the security_driver="selinux" in /etc/libvirt/qemu.conf
   security_driver = "selinux"
  #service libvirtd restart

5.Check the guest's status, found the guest disappear after restart the libvirtd service
# virsh list --all
 Id    Name                           State
----------------------------------------------------

#ps aux|grep rhel6u5

6.Check the libvirt log, find the following error:

# cat /var/log/libvirtd.log | grep -i qemuConnect
2014-08-21 07:28:41.178+0000: 4836: error : qemuConnectMonitor:1378 : Failed to set security context for monitor for rhel6u5









Verified this issue with libvirt-1.2.7-1.el7.x86_64:

1.Set security_driver=none in /etc/libvirt/qemu.conf
 security_driver = "none"
 #service libvirtd restart

2.Start a guest in the host
#virsh start rhel6u5
# virsh list
 Id    Name                           State
----------------------------------------------------
 1     rhel6u5                         running

3.Check the selinux label of the guest
# ps -efZ|grep rhel6u5
system_u:system_r:virtd_t:s0-s0:c0.c1023 qemu 5130 1 73 03:34 ?        00:00:01 /usr/libexec/qemu-kvm -name rhel6u5

# ll -Z /var/lib/libvirt/images/rhel6u5.img
-rw-------. qemu qemu system_u:object_r:virt_image_t:s0 /var/lib/libvirt/images/rhel6u5.img

4.Change the security_driver="selinux" in /etc/libvirt/qemu.conf
   security_driver = "selinux"
  #service libvirtd restart

5.Check the guest's status, found the guest is still running after restart the libvirtd service
# virsh list --all
 Id    Name                           State
----------------------------------------------------
1     rhel6u5                         running


6.Check the libvirt log, and not finding about selinux error.
Comment 5 zhenfeng wang 2014-11-25 05:40:31 UTC 
Verify this bug with libvirt-1.2.8-8.el7.x86_64
steps
1.Set security_driver=none in /etc/libvirt/qemu.conf
 security_driver = "none"
 #service libvirtd restart

2.Start a guest in the host
#virsh start rhel7.0
# virsh list
 Id    Name                           State
----------------------------------------------------
 1     rhel7.0                         running

3.Check the selinux label of the guest
# ps -efZ|grep qemu
system_u:system_r:virtd_t:s0-s0:c0.c1023 qemu 3922 1 13 13:26 ?        00:00:17 /usr/libexec/qemu-kvm -name rhel7.0

# ll /var/lib/libvirt/images/rhel7.0.qcow2  -Z
-rw-r--r--. root root system_u:object_r:virt_image_t:s0 /var/lib/libvirt/images/rhel7.0.qcow2


4.Change the security_driver="selinux" in /etc/libvirt/qemu.conf
   security_driver = "selinux"
  #service libvirtd restart

5.Check the guest's status, found the guest is still running after restart the libvirtd service
# virsh list --all
 Id    Name                           State
----------------------------------------------------
1     rhel7.0                         running

6.Check the libvirt log, and not finding about selinux error.

7.Destroy the guest, then re-start it
#virsh destroy rhel7.0
#virsh start rhel7.0

8.Check the selinux label of the guest
# ps -efZ|grep qemu
system_u:system_r:svirt_t:s0:c386,c692 qemu 4252   1 93 13:36 ?        00:00:08 /usr/libexec/qemu-kvm -name rhel7.0 

# ll -Z /var/lib/libvirt/images/rhel7.0.qcow2 
-rw-r--r--. qemu qemu system_u:object_r:svirt_image_t:s0:c386,c692 /var/lib/libvirt/images/rhel7.0.qcow2

9.Change the security_driver="none" in /etc/libvirt/qemu.conf
   security_driver = "selinux"
  #service libvirtd restart
10.Check the guest's status, found the guest is still running after restart the libvirtd service
# virsh list --all
 Id    Name                           State
----------------------------------------------------
1     rhel7.0                         running

# ps -efZ|grep qemu
system_u:system_r:svirt_t:s0:c386,c692 qemu 4252   1  9 13:36 ?        00:00:17 /usr/libexec/qemu-kvm -name rhel7.0

# ll -Z /var/lib/libvirt/images/rhel7.0.qcow2 
-rw-r--r--. qemu qemu system_u:object_r:svirt_image_t:s0:c386,c692 /var/lib/libvirt/images/rhel7.0.qcow2

11.Check the libvirt log, and not finding about selinux error.

According to the upper steps, mark this bug verifed
Comment 7 errata-xmlrpc 2015-03-05 07:36:54 UTC 
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/RHSA-2015-0323.html
Note You need to log in before you can comment on or make changes to this bug.