Hi all, I have had vmware running on my system for a couple of weeks. Tonight when starting vmware my system locked up (no keyboard or mouse response) and I had to press the reset key. After bring the system up when I attempt to 'power on' vmware I get a message that says: Could not open /dev/vmnet0: No such device. How do I make this device available? After the reboot it was necessary to issue 'insmod vmmon'. Thanks, Mike
Hi Mike, On my system, there's a file, /etc/init.d/vmware, which gets invoked when the machine boots. There are links to the file, thus: /etc/init.d/rc3.d/K22vmware -> ../vmware /etc/init.d/rc3.d/S01vmware -> ../vmware The two kernel modules that you need are vmmon and vmnet. If you don't have these modules in /lib/modules/your_kernel_rev/misc, then you'll need to rerun vmware-config.pl. Now, that should solve the problem of why they're not loading upon boot. However, I have no idea why your system locked up in the first place. Later, Andy -- Andy Stewart Founder Worcester Linux Users' Group Worcester, MA, USA http://www.wlug.org
After rerunning vmware-config.pl vmware ran again. However I think there may be a conflict between vmware and Oracle because my system locked up again when I started Oracle and then started vmware. Also I noticed your boot scripts are in /etc/init.d/ while mine are in /sbin/init.d/. What would account for this difference? I am running SuSE 7.0 Thanks, Mike On Friday 20 July 2001 08:50, you wrote:
Hi Mike,
On my system, there's a file, /etc/init.d/vmware, which gets invoked when the machine boots. There are links to the file, thus:
/etc/init.d/rc3.d/K22vmware -> ../vmware /etc/init.d/rc3.d/S01vmware -> ../vmware
The two kernel modules that you need are vmmon and vmnet. If you don't have these modules in /lib/modules/your_kernel_rev/misc, then you'll need to rerun vmware-config.pl.
Now, that should solve the problem of why they're not loading upon boot. However, I have no idea why your system locked up in the first place.
Later,
Andy
Michael Long said:
Also I noticed your boot scripts are in /etc/init.d/ while mine are in /sbin/init.d/. What would account for this difference? I am running SuSE 7.0
Different distributions put them in different places. /etc/inittab tells init where to look for the various files and whatnot. For example, Debian uses /etc/init.d/ for the actual scripts, and /etc/rcX.d for the various runlevels symlinks to the scripts, while RedHat, I believe, tosses everything in /etc/rc.d/ -- Aaron Haviland orion [at] tribble [dot] dyndns [dot] org orion [at] parsed [dot] net "Here I stand, foot in hand, talking to my wall. I'm not quite right at all, am I?" -Bowie.
On Friday 20 July 2001 23:55, Michael Long wrote:
After rerunning vmware-config.pl vmware ran again. However I think there may be a conflict between vmware and Oracle because my system locked up again when I started Oracle and then started vmware.
Also I noticed your boot scripts are in /etc/init.d/ while mine are in /sbin/init.d/. What would account for this difference? I am running SuSE 7.0
I am running SuSE 7.2 pro. According to /etc/init.d.README, the files were moved to /sbin/init.d per the Linux Standard Base specification. Andy
Thanks, Mike
On Friday 20 July 2001 08:50, you wrote:
Hi Mike,
On my system, there's a file, /etc/init.d/vmware, which gets invoked when the machine boots. There are links to the file, thus:
/etc/init.d/rc3.d/K22vmware -> ../vmware /etc/init.d/rc3.d/S01vmware -> ../vmware
The two kernel modules that you need are vmmon and vmnet. If you don't have these modules in /lib/modules/your_kernel_rev/misc, then you'll need to rerun vmware-config.pl.
Now, that should solve the problem of why they're not loading upon boot. However, I have no idea why your system locked up in the first place.
Later,
Andy
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
-- Andy Stewart Founder Worcester Linux Users' Group Worcester, MA, USA http://www.wlug.org
participants (3)
-
Aaron Haviland -
Andy Stewart -
Michael Long