View previous topic :: View next topic |
Author |
Message |
mrnato n00b
Joined: 10 May 2005 Posts: 13
|
Posted: Fri Dec 01, 2006 11:40 pm Post subject: No /dev/vmmon after reboot or Vmware complains of no vmmon |
|
|
I rebooted and vmware stopped working but everything was loading ok. Vmware complained of there being no /dev/vmmon but the vmmon module was loading. dmesg showed this
vmmon: no version magic, tainting kernel.
/dev/vmmon[5415]: Module vmmon: registered with major=10 minor=165
/dev/vmmon[5415]: Module vmmon: initialized
vmnet: no version magic, tainting kernel.
/dev/vmnet: open called by PID 5441 (vmnet-bridge)
/dev/vmnet: hub 0 does not exist, allocating memory.
/dev/vmnet: port on hub 0 successfully opened
and lsmod showed both vmnet and vmmon but still no /dev/vmmon
I reemerged and reran vmware-config.pl to no avail then found this solution on Centos site.
I found using VMware server or workstation on udev based linux kernel (2.6.x) hosts, that I had to re-run the vmware-config.pl script after every reboot - which is quite annoying when you want the guest OS to run as the service starts.
The issue is that due to udev being a dynamic system, nodes are wiped and re-created in /dev each boot. So the simple solution is to get the VMware init script to check for and re-create the nodes as required:
Add the following lines within the # just under the start line in /etc/init.d/vmware
start() {
# Start insert
if [ ! -e "/dev/vmmon" ]; then
mknod /dev/vmmon c 10 165
chmod 600 /dev/vmmon
fi
for a in `seq 0 9`; do
if [ ! -e "/dev/vmnet$a" ]; then
mknod /dev/vmnet$a c 119 $a
chmod 600 /dev/vmnet$a
fi
done
# End insert
test -x /etc/vmware/init.d/vmware || \
eend 1 "vmware init script not found. Aborting" || return 1
Which recreates the nodes that are required - just need VMware to pick that up for future versions.
Remember, you'll still need to re-run vmware-config.pl after a kernel upgrade.
Hope this helps someone one day cause it had me screwed for few hrs |
|
Back to top |
|
|
andrewd18 Guru
Joined: 11 Apr 2004 Posts: 364 Location: Wisconsin, USA
|
|
Back to top |
|
|
richfish Apprentice
Joined: 03 Mar 2006 Posts: 202 Location: Phoenix, AZ
|
Posted: Sun Dec 03, 2006 5:40 am Post subject: |
|
|
Which version of vmware are you using? With vmware-workstation-5.5.3.34685 and vmware-modules-1.0.0.15, I have a /etc/udev/rules.d/60-vmware.rules that lets udev create the device nodes correctly. It also includes a patched vmware-config.pl that doesn't actually rebuild the modules (you just remerge vmware-modules after kernel upgrades). |
|
Back to top |
|
|
EmmEff Apprentice
Joined: 17 Apr 2004 Posts: 197
|
Posted: Mon Dec 04, 2006 6:33 pm Post subject: |
|
|
I've got /etc/udev/rules.d/60-vmware.rules, vmware is added to the default runlevel, and it still demands re-running vmware-config.pl every time I reboot. Any other clues?
Thanks. |
|
Back to top |
|
|
richfish Apprentice
Joined: 03 Mar 2006 Posts: 202 Location: Phoenix, AZ
|
Posted: Mon Dec 04, 2006 7:11 pm Post subject: |
|
|
EmmEff wrote: | I've got /etc/udev/rules.d/60-vmware.rules, vmware is added to the default runlevel, and it still demands re-running vmware-config.pl every time I reboot. Any other clues?
Thanks. |
What version of workstation? I assume you have run it at least once? |
|
Back to top |
|
|
EmmEff Apprentice
Joined: 17 Apr 2004 Posts: 197
|
Posted: Mon Dec 04, 2006 8:22 pm Post subject: |
|
|
This is actually server (as it exists in Portage).
Yes, it's been run once and if I manually start it, it works fine. It just doesn't automatically start on reboot. Doesn't help either that I cannot see the console output. |
|
Back to top |
|
|
richfish Apprentice
Joined: 03 Mar 2006 Posts: 202 Location: Phoenix, AZ
|
Posted: Tue Dec 05, 2006 7:00 am Post subject: |
|
|
Ok, try this. The next time you boot and it gives you the "vmware-config.pl" message, do:
rm -vi /etc/vmware/not_configured
/etc/vmware/init.d/vmware start
And report the results. |
|
Back to top |
|
|
EmmEff Apprentice
Joined: 17 Apr 2004 Posts: 197
|
Posted: Tue Dec 05, 2006 3:34 pm Post subject: |
|
|
Interesting... I completely removed VMware Server from my system, manually cleaned/removed the directories, and reinstalled from Portage and it appears that it's working fine now. It starts at reboot. Is it possible this did not work initially and was fixed with a more recent version of the package? I didn't pay close attention to the versions. |
|
Back to top |
|
|
|