Bug 135084

Summary: vmware's /dev nodes dissappear
Product: [Fedora] Fedora Reporter: Joseph Harnish <jharnish>
Component: udevAssignee: Harald Hoyer <harald>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:06:14 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 Joseph Harnish 2004-10-08 15:12:31 UTC 
Description of problem:
I am running VMWare workstation on a FC3T2 host.  when I run
vmware-config.pl it creates a handful of nodes in /dev for use by the
virtual machines.  When I reboot these dissappear and I need to rerun
vmware-config.pl

Version-Release number of selected component (if applicable):


How reproducible:
every reboot

Steps to Reproduce:
1.  Install VMWare
2.  run vmware-config.pl
3.  run vmware (works fine)
4.  reboot
5.  run vmware (missing nodes in /dev)

  
Actual results:
missing nodes in /dev

Expected results:
vmware should start right up

Additional info:
Comment 1 Joseph Harnish 2004-10-08 15:14:30 UTC 
This could probably be fixed by changing the way VMWare works but it
might be nice if udev watches the /dev directory for new nodes being
added and adds them to a list of nodes that need to be generated on
reboot.
Comment 2 Warren Togami 2004-10-09 02:34:06 UTC 

*** This bug has been marked as a duplicate of 134641 ***
Comment 3 Harald Hoyer 2004-10-11 08:21:55 UTC 
the vmware kernel modules should provide a "dev" entry in the sysfs ...
Workaround:
manually copy the devices to /etc/udev/devices and they will be copied
on system start to /dev
see:
http://people.redhat.com/~harald/udev.html
Comment 4 Red Hat Bugzilla 2006-02-21 19:06:14 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.