Bug 521922
Summary: | setroubleshoot: SELinux is preventing vboxadd-service "read write" access on /dev/vboxadd. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jason <nospam> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | dwalsh, jeff.raber, mgrepl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | setroubleshoot_trace_hash:78ee0ef7e6d05c096ac0667dd47f5084dd570f4f8412a0f4ac2255111bbddbd1 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-05-16 20:52:06 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
Jason
2009-09-08 18:07:41 UTC
Looks like we need a polcy for vboxadd-service What is your VirtualBox release ? VirtualBox 3.04 - believe it was the latest version up until yesterday. This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Jason, Thank you for taking the time to report this bug. Updates to this package have been released since it was first reported. If you have time to update the package and re-test, please do so and report the results here. You can obtain the updated package by typing 'yum update selinux\*' or using the graphical updater, Software Update. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers It appears to be working properly now. No selinux errors that I see. Thank you! Closing as NOTABUG as the issue seems to be fixed, but no cause was identified in this bug. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers |