VMware Workstation 12.5.6 doesn't start on Ubuntu 17.10

[Loboar]

I upgraded to VMware Workstation 12.5.6 this morning but It does not start anymore. VMware's icon blinks in the unity launcher but vmware never starts.

I reinstalled it, reboot the computer, etc. Also, I installed kernel 4.11 but the issue was not solved.

If anyone of you can help me troubleshoot this issue I would appreciate it.

Now, I uninstalled that kernel and returned to previous 4.10.0-21-generic kernel. I will try to install the previous build of VMware Workstation which was running fine in the same computer but I would like to use 12.5.6 and know why that is not starting. Thanks.

Kind regards,

Hugo Javier Sanoguera

[dariusd]

Cool!  Your breadth of distro experience and experimentation is amazing.

Be aware that we still don't run on kernel 4.12...  We're still working up a fix for the issue reported in Linux Host: Kernel 4.12 Breaks vmmon.

As others have reported in that thread, it seems that the fix requires something beyond a simple code update... The "simple code update" causes a triple-fault and host reboot that we are still in the process of troubleshooting.

Cheers,

--

Darius

[mfelker]

I am running vmwarews 12.5.7 on Debian Sid with kernel 4.12.0-1-amd64.

All that it took to get this working was applyilng the attached shell script which is really pretty simple.  

If you could try it on Ubuntu 17.10 let me know. 

I am trying to find the author again - I'm pretty sure I posted his name before on this forum. 

[excolo]

just tried this on 17.10 and no luck... thanks for trying.

btw: here is the source of this patch, i think Tools/mkvmwmods.sh at master · cseader/Tools · GitHub

[excolo]

Here is some info on 17.10 that might be helpful, I just don't have much time to track it down at this point,

root@Galago-Pro:/tmp/vmware-root# tail vmware-3995.log

2017-08-29T19:21:39.279-05:00| modconfig| I125: Reading in info for the vmblock module.

2017-08-29T19:21:39.279-05:00| modconfig| I125: Reading in info for the vmci module.

2017-08-29T19:21:39.279-05:00| modconfig| I125: Reading in info for the vsock module.

2017-08-29T19:21:39.279-05:00| modconfig| I125: Setting vsock to depend on vmci.

2017-08-29T19:21:39.289-05:00| modconfig| I125: Trying to find a suitable PBM set for kernel "4.12.0-12-generic".

2017-08-29T19:21:39.289-05:00| modconfig| I125: No matching PBM set was found for kernel "4.12.0-12-generic".

2017-08-29T19:21:39.289-05:00| modconfig| I125: Found compiler at "/usr/bin/gcc"

2017-08-29T19:21:39.290-05:00| modconfig| I125: Got gcc version "7".

2017-08-29T19:21:39.290-05:00| modconfig| I125: Unable to parse gcc version

2017-08-29T19:21:39.292-05:00| modconfig| I125: We are now shutdown.  Ready to die!

Thanks all

[excolo]

We just upgraded to version 14 and all issues went away!!! Great Job!!

[gbolcer2]

These were the lib errors.

greg@salt:~$ vmware

/usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC symbol `clock_gettime'