Guys,
After updating to RHEL 7.4 (3.10.0-693.el7.x86_64), Workstation is unable to start. We get the "unable to start services" error. Its the same error we got previously as mentioned in this thread:
RHEL 6.8 64bit kernel update breaks Workstation
However, the "fix" suggested by ElCoyote_ is not working for us now:
Re: RHEL 6.8 64bit kernel update breaks Workstation
Our workaround right now is to boot to a previous kernel, then run the "fix" mentioned above. That gets our users back up and running.
Do you all have any suggestions for Workstation to start while booted with this kernel - 3.10.0-693.el7.x86_64 ?
Thanks
Hi,
Sorry to have forgotten to post here with my results.
The script /etc/init.d/vmware needs an extra hack because RHEL now includes vmw_* drivers by default.
The hack that worked for me was:
# diff -c vmware.orig vmware
*** vmware.orig 2017-08-01 12:33:02.438186297 -0400
--- vmware 2017-08-01 12:32:42.369169536 -0400
***************
*** 171,177 ****
mod_alias=$2
alias_file="/lib/modules/$(uname -r)/modules.alias"
! modname=$(/sbin/modprobe -R ${mod_alias} 2>/dev/null)
if [ $? = 0 -a "$modname" != "" ] ; then
echo $modname
elif grep -F ${mod_alias} ${alias_file} >/dev/null 2>&1 ; then
--- 171,177 ----
mod_alias=$2
alias_file="/lib/modules/$(uname -r)/modules.alias"
! modname=$(/sbin/modprobe -R ${mod_alias} 2>/dev/null|grep -v '^vmw_')
if [ $? = 0 -a "$modname" != "" ] ; then
echo $modname
elif grep -F ${mod_alias} ${alias_file} >/dev/null 2>&1 ; then
It would be nice if VMware could be more specific when 'grepping' for module names.
In this case, we have a collision between vmw_vmci.ko and vmci.ko from vmware.
Hello,
In addition to ElCoyote_'s edit of the /etc/init.d/vmware file, I borrowed the vmnet.ko file from another machine and placed it into /usr/lib/modules/3.10.0-693.1.1.el7.x86_64/misc/, ran 'depmod -a' then typed 'vmware' and the vm software started.
Yes, there still needs to be a source-level vmnet fix for el7.4. The /etc/init.d/vmware hack was something new in el7.4, though.
I am still having issues even if I attempt ElCoyote_ 's fix. I also tried scp'ing the vmnet.ko file and I do get a different error.
"Could not open /dev/vmmon: No such file or directory. Please make sure that the kernel module 'vmmon' is loaded."
VMWare says to disable secure boot in the BIOS, but UEFI isn't enabled on this machine. Its running on Legacy and doesn't even have the secure boot option.
Do you all see this error?