Hide Forgot
Description of problem: Mount net drive from rfremix 24 host with KVM/qemu to win 10 guest SELinux is preventing qemu-system-x86 from 'read' accesses on the directory XP. ***** Plugin catchall (100. confidence) suggests ************************** If вы считаете, что qemu-system-x86 следует разрешить доступ read к XP directory по умолчанию. Then рекомендуется создать отчет об ошибке. Чтобы разрешить доступ, можно создать локальный модуль политики. Do allow this access for now by executing: # ausearch -c 'qemu-system-x86' --raw | audit2allow -M my-qemusystemx86 # semodule -X 300 -i my-qemusystemx86.pp Additional Information: Source Context system_u:system_r:svirt_t:s0:c818,c920 Target Context unconfined_u:object_r:user_home_t:s0 Target Objects XP [ dir ] Source qemu-system-x86 Source Path qemu-system-x86 Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-191.21.fc24.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.8.8-200.fc24.x86_64 #1 SMP Tue Nov 15 19:41:51 UTC 2016 x86_64 x86_64 Alert Count 4 First Seen 2016-11-22 10:06:15 +05 Last Seen 2016-11-22 10:06:15 +05 Local ID a63f1217-cf98-4281-898e-d7beaa535022 Raw Audit Messages type=AVC msg=audit(1479791175.368:279): avc: denied { read } for pid=4184 comm="qemu-system-x86" name="XP" dev="dm-2" ino=36045376 scontext=system_u:system_r:svirt_t:s0:c818,c920 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=dir permissive=0 Hash: qemu-system-x86,svirt_t,user_home_t,dir,read Version-Release number of selected component: selinux-policy-3.13.1-191.21.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.8.8-200.fc24.x86_64 type: libreport Potential duplicate: bug 1196647
Description of problem: root@localhost: # ausearch -c 'qemu-system-x86' --raw | audit2allow -M my-qemusystemx86 compilation failed: my-qemusystemx86.te:23:ERROR 'syntax error' at token 'mlsconstrain' on line 23: # mlsconstrain file { ioctl read lock execute execute_no_trans } ((h1 dom h2 -Fail-) or (t1 != mcs_constrained_type -Fail-) ); Constraint DENIED mlsconstrain file { write setattr append unlink link rename } ((h1 dom h2 -Fail-) or (t1 != mcs_constrained_type -Fail-) ); Constraint DENIED /usr/bin/checkmodule: error(s) encountered while parsing configuration /usr/bin/checkmodule: loading policy configuration from my-qemusystemx86.te 10:37:04 @ 1 [~] root@localhost: # semodule -X 300 -i my-qemusystemx86.pp libsemanage.map_file: Unable to open my-qemusystemx86.pp (No such file or directory). libsemanage.semanage_direct_install_file: Unable to read file my-qemusystemx86.pp (No such file or directory). semodule: Failed on my-qemusystemx86.pp! Version-Release number of selected component: selinux-policy-3.13.1-191.21.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.8.8-200.fc24.x86_64 type: libreport
This directory on my Fedora 24 is not accessible now from win-10 VM via smb ((
Cutnioff, Where is XP dir stored?
(In reply to Lukas Vrabec from comment #3) > Cutnioff, > Where is XP dir stored? Hello! On Fedora-host (my Linux-workstation) where KVM/qemu installed. I try to mount network drive from Win10-VM. It was accessible some time earlier, but appeared inaccessible now (after system update probably). Samba works good.
(In reply to Lukas Vrabec from comment #3) > Cutnioff, > Where is XP dir stored? It is stored in my home directory many years during some installations of Fedora unconfined_u:object_r:user_home_t:s0 ~/XP
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.