Description of problem: Logs say: Sep 7 13:48:48 mbooth libvirtd: 13:48:48.174: error : qemudWaitForMonitor:1199 : internal error unable to start guest: bind(unix:/var/lib/libvirt/qemu/RHEL39FV32.monitor): Permission denied#012qemu: could not open monitor device 'unix:/var/lib/libvirt/qemu/RHEL39FV32.monitor,server,nowait'#012 AVC says: node=mbooth.laptop type=AVC msg=audit(1252325368.622:35846): avc: denied { write } for pid=12710 comm="qemu-kvm" name="qemu" dev=dm-1 ino=82074 scontext=system_u:system_r:svirt_t:s0:c523,c571 tcontext=system_u:object_r:virt_var_lib_t:s0 tclass=dir node=mbooth.laptop type=SYSCALL msg=audit(1252325368.622:35846): arch=c000003e syscall=49 success=no exit=-13 a0=a a1=7fff3ecd2230 a2=6e a3=7fff3ecd1fc0 items=0 ppid=12709 pid=12710 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="qemu-kvm" exe="/usr/bin/qemu-kvm" subj=system_u:system_r:svirt_t:s0:c523,c571 key=(null) Notice how it is trying to open a monitor device under /var/lib/. This doesn't look right, I would expect this to be in /var/run. In fact, the SELinux targeted policy contains the following: /var/run/libvirt/qemu(/.*)? gen_context(system_u:object_r:svirt_var_run_t,s0) Changing the context of /var/lib/libvirt/qemu to system_u:object_r:svirt_var_run_t:s0 allows guests to start again. It would appear that libvirt is putting this monitor file in the wrong place. Version-Release number of selected component (if applicable): libvirt-0.7.1-0.1.git3ef2e05.fc11.x86_64 selinux-policy-targeted-3.6.12-81.fc11.noarch How reproducible: Always Steps to Reproduce: 1. Open Virtual Machine Manager 2. Select a guest 3. Click Run
Thanks Matt The monitor socket has moved to /var/lib/libvirt/qemu because of this: http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=182a80b922
Fixed in selinux-policy-3.6.30-6.fc12.noarch
*** Bug 522697 has been marked as a duplicate of this bug. ***
*** Bug 524887 has been marked as a duplicate of this bug. ***
------- Comment From santwana.samantray.com 2009-10-27 02:35 EDT------- Hi, I verified this issue in the latest F12 rawhide release(k.v- 2.6.31.5-96.fc12.x86_64), and the issue seems to be fixed. When selinux was enabled, the guest installation started without any problems using virt-install. [root@mx3550 ~]# getenforce Enforcing [root@mx3550 ~]# virt-install -n rhel61 -r 500 --vcpus 2 --virt-type=kvm -c /home/RHEL6.0-20091021.0-x86_64-DVD1.iso --disk path=/var/lib/libvirt/images/rhel6.raw --vnc Starting install... Creating domain... | 0 B 00:00 Domain installation still in progress. You can reconnect to the console to complete the installation process. Below are the versions installed: selinux-policy-targeted-3.6.32-27.fc12.noarch libvirt-0.7.1-13.fc12.x86_64 python-virtinst-0.500.0-5.fc12.noarch Thanks, Santwana