Hide Forgot
SELinux is preventing /usr/bin/python from 'write' accesses on the directory /. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that python should be allowed write access on the directory by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep xm /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:virsh_t:s0 Target Context system_u:object_r:root_t:s0 Target Objects / [ dir ] Source xm Source Path /usr/bin/python Port <Unknown> Host (removed) Source RPM Packages python-2.7-8.fc14.1 Target RPM Packages realplay-11.0.2.1744-1 Policy RPM selinux-policy-3.9.7-40.fc14 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 2.6.35.13-92.fc14.x86_64 #1 SMP Sat May 21 17:26:25 UTC 2011 x86_64 x86_64 Alert Count 6 First Seen Fri 10 Jun 2011 10:49:37 PM MDT Last Seen Sat 18 Jun 2011 08:34:39 PM MDT Local ID 06c77622-784f-4309-b47f-24a8a3eee98c Raw Audit Messages type=AVC msg=audit(1308450879.756:15): avc: denied { write } for pid=2106 comm="xm" name="/" dev=dm-1 ino=2 scontext=system_u:system_r:virsh_t:s0 tcontext=system_u:object_r:root_t:s0 tclass=dir type=SYSCALL msg=audit(1308450879.756:15): arch=x86_64 syscall=open success=no exit=EACCES a0=dc6e60 a1=200c2 a2=180 a3=1 items=0 ppid=2105 pid=2106 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=xm exe=/usr/bin/python subj=system_u:system_r:virsh_t:s0 key=(null) Hash: xm,virsh_t,root_t,dir,write audit2allow #============= virsh_t ============== #!!!! The source type 'virsh_t' can write to a 'dir' of the following types: # ssh_home_t, xend_var_lib_t, virt_etc_t, virt_etc_rw_t, virt_image_type, xenfs_t, nfs_t allow virsh_t root_t:dir write; audit2allow -R #============= virsh_t ============== #!!!! The source type 'virsh_t' can write to a 'dir' of the following types: # ssh_home_t, xend_var_lib_t, virt_etc_t, virt_etc_rw_t, virt_image_type, xenfs_t, nfs_t allow virsh_t root_t:dir write;
Which command does this AVC cause?
I noticed the AVC after booting; I'm not sure which command is triggering the AVC. How would I find that out?
This looks like xm is running and thinking its homedir is /?
Please reopen if this still happens.