Summary:

SELinux is preventing /usr/bin/vmnet-bridge "read write" access to device
vmnet0.

Detailed Description:

SELinux has denied vmnet-bridge "read write" access to device vmnet0. vmnet0 is
mislabeled, this device has the default label of the /dev directory, which
should not happen. All Character and/or Block Devices should have a label. You
can attempt to change the label of the file using restorecon -v 'vmnet0'. If
this device remains labeled device_t, then this is a bug in SELinux policy.
Please file a bg report. If you look at the other similar devices labels, ls -lZ
/dev/SIMILAR, and find a type that would work for vmnet0, you can use chcon -t
SIMILAR_TYPE 'vmnet0', If this fixes the problem, you can make this permanent by
executing semanage fcontext -a -t SIMILAR_TYPE 'vmnet0' If the restorecon
changes the context, this indicates that the application that created the
device, created it without using SELinux APIs. If you can figure out which
application created the device, please file a bug report against this
application.

Allowing Access:

Attempt restorecon -v 'vmnet0' or chcon -t SIMILAR_TYPE 'vmnet0'

Additional Information:

Source Context                system_u:system_r:vmware_host_t:s0-s0:c0.c1023
Target Context                system_u:object_r:device_t:s0
Target Objects                vmnet0 [ chr_file ]
Source                        vmnet-dhcpd
Source Path                   /usr/bin/vmnet-dhcpd
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.6.32-108.fc12
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Plugin Name                   device
Host Name                     (removed)
Platform                      Linux (removed)
                              2.6.31.12-174.2.22.fc12.i686.PAE #1 SMP Fri Feb 19
                              19:10:04 UTC 2010 i686 athlon
Alert Count                   57
First Seen                    Fri 09 Apr 2010 05:28:53 PM IRDT
Last Seen                     Sat 10 Apr 2010 02:16:25 PM IRDT
Local ID                      ba815c92-bb50-4b4e-a3ae-a71deb8a9210
Line Numbers                  

Raw Audit Messages            

node=(removed) type=AVC msg=audit(1270892785.379:48): avc:  denied  { read write } for  pid=1423 comm="vmnet-bridge" name="vmnet0" dev=tmpfs ino=10691 scontext=system_u:system_r:vmware_host_t:s0-s0:c0.c1023 tcontext=system_u:object_r:device_t:s0 tclass=chr_file

node=(removed) type=SYSCALL msg=audit(1270892785.379:48): arch=40000003 syscall=5 success=no exit=-13 a0=9ea24b8 a1=8002 a2=0 a3=ffffffff items=0 ppid=1 pid=1423 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="vmnet-bridge" exe="/usr/bin/vmnet-bridge" subj=system_u:system_r:vmware_host_t:s0-s0:c0.c1023 key=(null)



Hash String generated from  device,vmnet-dhcpd,vmware_host_t,device_t,chr_file,read,write
audit2allow suggests:

#============= vmware_host_t ==============
allow vmware_host_t device_t:chr_file { read write };