Created attachment 342770 [details] SELinux alert Description of problem: Installing libvirt on a Fedora 11 + rawhide system and starting the libvirt service for the first time causes SELinux alerts: SELinux is preventing libvirtd from using potentially mislabelled files (root) Version-Release number of selected component (if applicable): libvirt-0.6.2-4.f11.x86_64 selinux-policy-targetted-3.6.12-28.fc11.noarch How reproducible: Occurs only the first time libvirt is started. subsequent "service libvirt restart" does not show up the SELinux alerts. Steps to Reproduce: 1. Install Fedora Rawhide (7 May) 2. Install libvirt: System-> Administration ->Add/Remove Software-> check all virtualization components 3. Start libvirt Actual results: libvirt starts with no SELinux alerts Expected results: libvirt starts with 3 SELinux alerts on access to root [ dir ] Additional info: SELinux alert attached.
Okay, looks like the UML is writing to /root/ if (virAsprintf(¨_driver->monitorDir, "%s/.uml", userdir) == -1) goto out_of_memory; Thanks Charles
Why? This should go into /var/lib/libvirt/ If possible.
Hmm, I thought that ~/.uml/ was compiled into the UserModeLinux kernel. Looking at the kernel source now, it turns out that you can pass a kernel boot argument to UML to override this, so we could force it to be created under /var/run/libvirt/uml as we do with QEMU.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
*** Bug 531500 has been marked as a duplicate of this bug. ***
*** Bug 553013 has been marked as a duplicate of this bug. ***
FYI, the kernel option Dan is talking about seems to be uml_dir= : http://user-mode-linux.sourceforge.net/old/switches.html
Yep, I got 1/2 way through fixing this, but then found that Fedora can't build any current UML kernel because of a issue in base 4.0. so was unable to test it works !
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11'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 11 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
Still relevant for F12.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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
I believe this is fixed upstream: 0a58eed3d9d51d28c4e1d69e8dbe334779f447e0 Moving to F14
*** Bug 589363 has been marked as a duplicate of this bug. ***
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
F14 is EOL, please reopen if this is still relevant in a more recent fedora.