Description of problem: I've tried xen para virtualization on F18Beta-TC7. Installation was successful but after click on reboot, warning dialog show up: xend_post: error from xen daemon: (xend.err "Disk isn't accessible") in audit log: type=AVC msg=audit(1352130837.961:1311): avc: denied { read } for pid=20763 comm="xend" name="f16.img" dev="dm-1" ino=1443701 scontext=system_u:system_r:xend_t:s0 tcontext=system_u:object_r:virt_image_t:s0 tclass=file type=SYSCALL msg=audit(1352130837.961:1311): arch=c000003e syscall=21 success=no exit=-13 a0=7f9bd40ddd70 a1=4 a2=7f9c0b908a08 a3=20 items=0 ppid=1 pid=20763 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="xend" exe=2F7573722F62696E2F707974686F6E322E37202864656C6574656429 subj=system_u:system_r:xend_t:s0 key=(null) Version-Release number of selected component (if applicable): selinux-policy-3.11.1-46.fc18.noarch selinux-policy-targeted-3.11.1-46.fc18.noarch xen-hypervisor-4.2.0-3.fc18.x86_64 xen-libs-4.2.0-3.fc18.x86_64 xen-4.2.0-3.fc18.x86_64 xen-licenses-4.2.0-3.fc18.x86_64 xen-runtime-4.2.0-3.fc18.x86_64 libvirt-daemon-driver-xen-0.10.2.1-2.fc18.x86_64 How reproducible: Steps to Reproduce: 1. on Fedora-18-Beta-TC7 install xen virtualization 2. install e.g. fedora16 guest, reboot guest Actual results: type=AVC msg=audit(1352129887.015:1037): avc: denied { read } for pid=12901 comm="xend" name="para.img" dev="dm-1" ino=1443697 scontext=system_u:system_r:xend_t:s0 tcontext=system_u:object_r:virt_image_t:s0 tclass=file Expected results: no AVC denial Additional info:
If you change the label to xen_image_t this should work fine. chcon -t xen_image_t para.img f16.img Can you run this from libvirt?
I've changed label and it works now. I used virt-manager for system installation.
Ok so this xen image is located in the /var/lib/libvirt/images by default in your case, right?
yes
Maybe we should just allow xend to manager virt_image_t.
I agree. Added to selinux-policy-3.11.1-52.fc18
selinux-policy-3.11.1-57.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/selinux-policy-3.11.1-57.fc18
Package selinux-policy-3.11.1-57.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.11.1-57.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19374/selinux-policy-3.11.1-57.fc18 then log in and leave karma (feedback).
Package selinux-policy-3.11.1-59.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.11.1-59.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19374/selinux-policy-3.11.1-59.fc18 then log in and leave karma (feedback).
Package selinux-policy-3.11.1-60.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.11.1-60.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19374/selinux-policy-3.11.1-60.fc18 then log in and leave karma (feedback).
selinux-policy-3.11.1-60.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.