/etc/init.d/vmware loads only the vmci module of vmware-modules. There is, however, the alternative to use the in-kernel versions of vmci and vsock instead of the ones supplied by vmware-modules. Unfortunately the in-kernel version of vmci is named vmw_vmci so /etc/init.d/vmware needs to detect, which of the modules, either vmci or vmw_vmci is available and load the proper module. See also bug 501536 which enhances vmware-modules to allow the use of the in-kernel modules. Probably vmware-player is affected to but I do not use it thus I can't tell. Reproducible: Always
OK this one is a bit tricky. Thinking...
*** Bug 508154 has been marked as a duplicate of this bug. ***
I think it would be more straight forward if all the module based systemd service files were supplied by vmware-modules which already has the use flags.
Fixed without revision bump, please just re-emerge vmware-workstation
To stop error message "FATAL: Module vmci not found" --- /etc/init.d/vmware 2014-05-09 09:27:47.000000000 +0300 +++ /etc/init.d/vmware-mod 2014-05-09 09:28:18.000000000 +0300 @@ -16,7 +16,7 @@ ebegin Starting VMware services modprobe -v vmci || modprobe -v vmw_vmci eend $? - modprobe -av vmmon vmci vsock vmblock vmnet + modprobe -av vmmon vsock vmblock vmnet eend $? /opt/vmware/bin/vmware-networks --start eend $?
