Bug 450863 - Piles of AVCs when starting a virtual machine
Piles of AVCs when starting a virtual machine
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
9
All Linux
low Severity low
: ---
: ---
Assigned To: Daniel Walsh
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-11 10:21 EDT by Casey Dahlin
Modified: 2014-06-18 04:46 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-11-17 16:53:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Casey Dahlin 2008-06-11 10:21:20 EDT
I get these when starting a qemu-kvm virtual machine from virtmanager. They come
hundreds at a time, I think I got about 1700 when I booted.

Raw Audit Messages
host=4chan type=AVC msg=audit(1213193183.890:47492): avc:  denied  { getsched }
for  pid=31214 comm="qemu-system-x86" scontext=system_u:system_r:virtd_t:s0
                tcontext=system_u:system_r:virtd_t:s0 tclass=process
host=4chan type=SYSCALL msg=audit(1213193183.890:47492): arch=c000003e
syscall=145 success=no exit=-13 a0=79ee a1=7fcdc3acaae8 a2=d a3=0 items=0
ppid=2362 pid=31214 auid=4294967295 uid=0 gid=0
                euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none)
ses=4294967295 comm="qemu-system-x86" exe="/usr/bin/qemu-system-x86_64"
subj=system_u:system_r:virtd_t:s0 key=(null)
Comment 1 Daniel Walsh 2008-06-14 07:12:01 EDT
# audit2allow -M mypol -l -i /var/log/audit/audit.log
# semodule -i mypol.pp

Fixed in selinux-policy-3.3.1-67.fc9.noarch
Comment 2 Casey Dahlin 2008-11-17 16:39:14 EST
This does indeed seem fixed. I see no reason to keep this open. Dan, do you agree?
Comment 3 Daniel Walsh 2008-11-17 16:53:23 EST
When you confirm you are welcome to close.

Note You need to log in before you can comment on or make changes to this bug.