This bug has been copied from bug #896013 and has been proposed to be backported to 6.4 z-stream (EUS).
In POST: http://post-office.corp.redhat.com/archives/rhvirt-patches/2013-February/msg00239.html
*** Bug 919074 has been marked as a duplicate of this bug. ***
*** Bug 910806 has been marked as a duplicate of this bug. ***
The patch resolved the AVCs in 910806 / 919074
Verify this bug with: libvirt-0.10.2-18.el6_4.1.x86_64 qemu-kvm-rhev-0.12.1.2-2.355.el6_4.2.x86_64 1)stop cgroup service #service cgconfig stop 2) restart libvirtd service #service libvirtd restart 3) start a domain #virsh start bug Domain bug started 4) create a disk-only snapshot # virsh snapshot-create-as --disk-only bug s1 Domain snapshot s1 created 5)check images ]# ll -Z /mnt/sda5/images/bug.* -rw-------. qemu qemu unconfined_u:object_r:svirt_image_t:s0:c100,c954 /mnt/sda5/images/bug.img -rw-------. qemu qemu unconfined_u:object_r:svirt_image_t:s0:c100,c954 /mnt/sda5/images/bug.s1 6)restart guest # virsh destroy bug Domain bug destroyed # virsh start bug Domain bug started 7)# service cgconfig status Stopped
The patch for this bug causes a regression (bug 922683), which we need to fix.
Back in POST to pull in the regression fix: http://post-office.corp.redhat.com/archives/rhvirt-patches/2013-March/msg00195.html
Verify this bug with : libvirt-0.10.2-18.el6_4.2.x86_64 vdsm-4.10.2-1.8.el6ev.x86_64 scenario 1: PASS 1)stop cgroup service #service cgconfig stop 2) restart libvirtd service #service libvirtd restart 3) start a domain #virsh start bug Domain bug started 4) create a disk-only snapshot # virsh snapshot-create-as --disk-only bug s3 Domain snapshot s3 created 6)restart guest # virsh destroy bug Domain bug destroyed # virsh start bug Domain bug started 7)# service cgconfig status Stopped scenario 2(BZ 922683): PASS 1.Prepare a iscsi storage in rhevm , install a guest in it 2.Active a iso domain , add it's iso into the guest 3.inActive the iso domain , then migrate the guest it can succeed
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. http://rhn.redhat.com/errata/RHBA-2013-0664.html
*** Bug 957276 has been marked as a duplicate of this bug. ***
*** Bug 973160 has been marked as a duplicate of this bug. ***