Bug 589363
| Summary: | SELinux empêche l'accès en "write" à /usr/sbin/libvirtd on /ro | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Carl G. <carlg> |
| Component: | libvirt | Assignee: | Daniel Veillard <veillard> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 13 | CC: | berrange, clalance, crobinso, dwalsh, itamar, jeff.raber, jforbes, johannbg, mgrepl, renich, veillard, virt-maint, xurzwi2q1 |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | setroubleshoot_trace_hash:3e4801a31e018462c00c2e7bc7de45e3cd93b65a27378f10be1a9eb01c1db4fb | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-10 17:34:56 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: | |||
|
Description
Carl G.
2010-05-05 23:07:10 UTC
libvirtd fail to start during the boot procedure. Why is libvirt trying to write to /root? Did you put an image file in that directory? Is there something in libvirt database that refers to /root? The only thing i did was to : 1) Create a storage pool (in my home dir (carl) labeled svirt_image_t libvirtd is configured to start with my system but it fail to do so and that's the AVC i get when i run sudo to start it. I can also attach libvirt / qemu config but i don't think you will find anything interresting. I don't see anything in /root that could be related to virt. This would be a libvirt issue then sudo /etc/init.d/libvirtd restart Arrêt du démon libvirtd : [ OK ] Démarrage du démon libvirtd : [ OK ] May 6 11:19:30 libvirtd: 11:19:30.668: warning : qemudDispatchSignalEvent:385 : Shutting down on signal 15 May 6 11:19:30 libvirtd: Could not find keytab file: /etc/libvirt/krb5.tab: No such file or directory May 6 11:19:30 libvirtd: 11:19:30.908: error : udevStrToLong_ui:78 : Failed to convert 'ff' to unsigned int May 6 11:19:30 libvirtd: 11:19:30.925: warning : qemudStartup:1150 : Unable to create cgroup for driver: No such device or address May 6 11:19:31 kernel: lo: Disabled Privacy Extensions May 6 11:19:31 libvirtd: 11:19:31.056: warning : lxcStartup:1748 : Unable to create cgroup for driver: No such device or address May 6 11:19:31 libvirtd: 11:19:31.056: error : umlStartup:422 : Failed to create monitor directory /root/.uml: Permission denied May 6 11:19:31 libvirtd: 11:19:31.065: error : virStateInitialize:890 : Initialization of UML state driver failed May 6 11:19:31 libvirtd: 11:19:31.065: error : main:3160 : Driver state initialization failed May 6 11:19:31 libvirtd: 11:19:31.065: warning : qemudDispatchSignalEvent:385 : Shutting down on signal 3 May 6 11:19:33 setroubleshoot: SELinux empêche l'accès en "write" à /usr/sbin/libvirtd on /root. For complete SELinux messages. run sealert -l 0ad4bec9-784a-4f95-aecf-c82fd3731eae libvirt-0.7.7-3.fc13.x86_64 We need to trick libvirt into seeing its homedir as something other then /root Why does it matter what its working directory is ? AFAIK libvirt isn't attempting to create files in its CWD. I'd prefer to know what is being written to /root before simply moving the working directory elsewhere. (In reply to comment #8) > Why does it matter what its working directory is ? AFAIK libvirt isn't > attempting to create files in its CWD. I'd prefer to know what is being written > to /root before simply moving the working directory elsewhere. ls -l /root/.uml total 0 Once the directory is created, everything seems to be fine. libvirtd is trying to create the directory .uml in /root. Daniel I can give libvirt the rights to write to this directory. And we can add a label for .uml. But is seems to me that these directories/files get created based on libraries that libvirt calls, and does not necessarily control. Changing $HOMEDIR to /var/lib/libvirt Would allow libvirt and any libraries it executes the ability to write and manipulate stuff, with less risk of mislabeled content. Ok, the UML problem is also reported in Fedora 11 as bug 499536. In theory we can move this directory, but I need to actually do some tests to make sure it'll work. If possible we'll move it to /var/run/libvirt/uml to match the qemu location. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 WONTFIX if it remains open with a Fedora 'version' of '13'. 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 prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Duping to 499536 *** This bug has been marked as a duplicate of bug 499536 *** |