Bug 1275603
Summary: | SELinux is preventing qemu-system-x86 from 'write' accesses on the directory lib. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mathieu Bridon <bochecha> |
Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 23 | CC: | awilliam, dominick.grift, dwalsh, kparal, lvrabec, mgrepl, plautrba, robatino, sgallagh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:696e0794213ed97b907fed3bdb6860e34719d5fd1c43eddff71c9dc39d2091f8;VARIANT_ID=workstation; | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-27 16:57:51 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1170821 |
Description
Mathieu Bridon
2015-10-27 10:13:02 UTC
Proposed as a Blocker for 23-final by Fedora user bochecha using the blocker tracking app because: SELinux prevents GNOME Boxes from creating a virtual machine, which I would qualify as "basic functionality" for that application. This violates the "Default application functionality" release criteria. I tried but couldn't reproduce this. I installed clean F23 RC3 Workstation Live, then used the same ISO image to install it inside Boxes. The VM boots fine both Live and installed, no SELinux alerts. I have the same kernel and selinux-policy version as OP. Stephen Gallagher also tried to reproduce, also received no AVCs. *** Bug 1275607 has been marked as a duplicate of this bug. *** *** Bug 1275605 has been marked as a duplicate of this bug. *** I'm -1 blocker on this, since I can't reproduce it and I've tried. Also, it's worth noting that all of the files referenced in these bugs are located within the user's home directory. It's possible that something got mislabeled if this home directory was reused or is hosted on NFS, etc. But it seems that it's not an issue for a freshly-installed system. Hi Mathieu, Did you try it on fresh installation? I believe you turn selinux off, then reboot system and then turn selinux on again. Please run: "# restorecon -R -v /" This should fix your issue. Thank you guys for testing. (In reply to Stephen Gallagher from comment #6) > Also, it's worth noting that all of the files referenced in these bugs are > located within the user's home directory. It's possible that something got > mislabeled if this home directory was reused or is hosted on NFS, etc. But > it seems that it's not an issue for a freshly-installed system. This is fresh new install, I did not reuse the home folder, it is not on NFS. (In reply to Lukas Vrabec from comment #7) > Hi Mathieu, > > Did you try it on fresh installation? Yes. > I believe you turn selinux off, then > reboot system and then turn selinux on again. I never turned SELinux off on this system since I installed it last Thursday. I only did "setenforce 0" **after** I started running into this bug, because I needed the VM to do some work. > Please run: > "# restorecon -R -v /" Ok, I just did that. Indeed, it restored the context of some files under ~/.local/share/gnome-boxes and ~/.config/libvirt And now I don't seem to get any SELinux errors any more, so it was indeed a problem with mislabled files. I'm really wondering why those files got mislabeled, though, but I guess that's not this bug. Thanks. How did you do your install, Mathieu? I downloaded the latest (as of last Thursday morning, UTC+2) Workstation image from https://alt.fedoraproject.org/pub/alt/stage/?C=M;O=A Then made a live USB, and installed the usual way. Nothing special really. If we are not able to reproduce, I would close this bug. It could be some specific/install issue which caused you got unlabeled_t for some dirs/files related to gnome-boxes and libvirt. If we get a reproducer then we will investigate further. Thanks. mathieu: can you post the exact image filename? That's safer than me trying to guess what you would have downloaded last Thursday. |