Bug 1102612

+++ This bug was initially created as a clone of Bug #1102611 +++

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: