:smileycry::smileycry::smileycry::smileycry::smileycry::smileycry: Anybody knows about this problem ???
For me vmmon was not starting after the upgrade to 6.6, it complained about a mismatch with poll_initwait.
After checking the log files I found that vmware-modconfig was using the pre built modules for the 6.5 kernel instead of building new ones.
I tried manually building each module and everything seems to work again.
try "vmware-modconfig --console --build-mod vmmon" repeating for each module.
Thank you very match. I'll try this method.
Nope, it hasn't worked for me yet. Had to simply go back to the RHEL 6.5 kernel. No biggie.
There'll be a fix in soon I'm sure.
Hi!
look the post from aalesilva Oct 22, 2014 -> and comments from raz3k - about this problem
Hi ahaines69,
The work-around you introduced in this post worked for my environment, CentOS 6.6.
Thanks!
Regards,
Ta-chang
Does that fix survive a reboot? On my system the modules are built on the fly at boot time. So rebuilding them would have to be done after every reboot.
Had the same problem after upgrading to 6.6.
The VMware virtual machine monitor would not load. I got
modprobe vmmon
FATAL: Error inserting vmmon (/lib/modules/2.6.32-504.el6.x86_64/misc/vmmon.ko): Unknown symbol in module, or unknown parameter (see dmesg)
desg has;
vmmon: disagrees about version of symbol poll_initwait
vmmon: Unknown symbol poll_initwait
vmmon: disagrees about version of symbol poll_freewait
vmmon: Unknown symbol poll_freewait
I un-installed and re-installed WS10 to no avail.
So I rebuilt the modules with these commands
vmware-modconfig --console --build-mod vmmon
vmware-modconfig --console --build-mod vmnet
vmware-modconfig --console --build-mod vmci
Then reloaded the modules
modprobe vmmon
modprobe vmnet
modprobe vmci
Now I get;
[root@gemini ~]# service vmware restart
Stopping VMware services:
VMware Authentication Daemon [ OK ]
VM communication interface socket family [ OK ]
Virtual machine communication interface [ OK ]
Virtual machine monitor [ OK ]
Blocking file system [ OK ]
Starting VMware services:
Virtual machine monitor [ OK ]
Virtual machine communication interface [ OK ]
VM communication interface socket family [ OK ]
Blocking file system [ OK ]
Virtual ethernet [ OK ]
VMware Authentication Daemon [ OK ]
Shared Memory Available [ OK ]
[root@gemini ~]#
Hope this helps
Does that fix survive a reboot?
Hi mntnbighker,
I've checked your concern on my environment and no serious problem was found.
Trivial one was that all VM inventory existed was erased after reboot
although I've not still known the real reason for it until now...
Regards,
Ta-chang
I've observed this issue for a while and found the inventory settings were compulsorily initialized
every time after reboot.
Does anyone know the root cause of and how to fix it?
Ta-chang
I finally broke down and used the script to rebuild the vmware modules since no vmware patch has been forthcoming, and now that another CentOS kernel has been released that still breaks Workstation. The fix appears to survive a reboot, but I saw the following after the first reboot. The VM's appear to work despite all the backtrace messages.
Rebuilding the modules works for me
echo vmblock vmci vmmon vmnet vsock|xargs -n1 vmware-modconfig --console --build-mod
Only had to rebuild vmmon, but may as well do the lot. Hope that helps!