VMware – 14.1.0 released – OK with Kernel 4.14, Still Broken with 4.15, and a Nasty Hack to Fix..

Just updated to VMware Workstation 14.1.0, and release notes are here:  https://docs.vmware.com/en/VMware-Workstation-Pro/14.0.0/rn/workstation-141-release-notes.html

This now works OK with Kernel 4.14 (tested with 4.14.8) but vmmon is still broken with Kernel 4.15 (tested with 4.15-rc4):

................
/tmp/modconfig-04hK9s/vmmon-only/linux/hostif.c: In function ‘HostIF_InitUptime’:
/tmp/modconfig-04hK9s/vmmon-only/linux/hostif.c:1770:4: error: implicit declaration of function ‘init_timer’; did you mean ‘init_timers’? [-Werror=implicit-function-declaration]
 init_timer(&uptimeState.timer);
 ^~~~~~~~~~
 init_timers
/tmp/modconfig-04hK9s/vmmon-only/linux/hostif.c:1771:31: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types]
 uptimeState.timer.function = HostIFUptimeResyncMono;
 ^
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:310: /tmp/modconfig-04hK9s/vmmon-only/linux/hostif.o] Error 1
make[1]: *** [Makefile:1502: _module_/tmp/modconfig-04hK9s/vmmon-only] Error 2
make[1]: Leaving directory '/usr/src/linux-4.15-rc4'
make: *** [Makefile:110: vmmon.ko] Error 2
make: Leaving directory '/tmp/modconfig-04hK9s/vmmon-only'
.......................
etc... etc...

As the compile fail appeared to be similar to the one with VMware 4.0.0 – for which a patch is available – I was able to do a ‘nasty hack‘ by creating and then applying a patch-set from the 4.15-patched VMware 4.0.0 versions of vmmon-only/linux/hostif.c and driver.c, against their VMware 4.1.0 equivalents, and copying across the ‘new’ header file vmmon-only/include/compat_timer.h.   This did work, but is – obviously – not an ideal solution, and hopefully someone with the necessary skills will be able to produce a ‘proper’ patch, soon..

Robert Gadsdon.  December 21, 2017.


Comments

VMware – 14.1.0 released – OK with Kernel 4.14, Still Broken with 4.15, and a Nasty Hack to Fix.. — 3 Comments

  1. FYI: VMWare 14.1 is now broken with Kernel 4.14.9. I reckon it’s the same issue as 4.15 but didn’t spend time yet looking into it.

    • VMware 14.1.0 is OK on my system with Kernel 4.14.9, but NVIDIA _is_ broken.. I’m preparing more info for an article, now..
      RG.

  2. Vmware 14.1.1 does not install correct on Linux 4.14.18-300.fc27.x86_64 Fedora release 27

    Went back to older kernelversion that is supported.

    Logfile of vmware-root:

    2018-02-13T10:27:06.625+01:00| modconfig| I125: Log for VMware Workstation pid=2959 version=14.1.1 build=build-7528167 option=Release
    2018-02-13T10:27:06.625+01:00| modconfig| I125: The process is 64-bit.
    2018-02-13T10:27:06.625+01:00| modconfig| I125: Host codepage=UTF-8 encoding=UTF-8
    2018-02-13T10:27:06.625+01:00| modconfig| I125: Host is Linux 4.14.18-300.fc27.x86_64 Fedora release 27 (Twenty Seven)
    2018-02-13T10:27:06.625+01:00| modconfig| I125: DictionaryLoad: Cannot open file “/usr/lib/vmware/settings”: No such file or directory.
    2018-02-13T10:27:06.625+01:00| modconfig| I125: [msg.dictionary.load.openFailed] Cannot open file “/usr/lib/vmware/settings”: No such file or directory.
    2018-02-13T10:27:06.625+01:00| modconfig| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
    2018-02-13T10:27:06.625+01:00| modconfig| I125: DictionaryLoad: Cannot open file “/usr/lib/vmware/config”: No such file or directory.
    2018-02-13T10:27:06.625+01:00| modconfig| I125: [msg.dictionary.load.openFailed] Cannot open file “/usr/lib/vmware/config”: No such file or directory.
    2018-02-13T10:27:06.625+01:00| modconfig| I125: PREF Optional preferences file not found at /usr/lib/vmware/config. Using default values.
    2018-02-13T10:27:06.625+01:00| modconfig| I125: DictionaryLoad: Cannot open file “/root/.vmware/config”: No such file or directory.
    2018-02-13T10:27:06.625+01:00| modconfig| I125: [msg.dictionary.load.openFailed] Cannot open file “/root/.vmware/config”: No such file or directory.
    2018-02-13T10:27:06.625+01:00| modconfig| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
    2018-02-13T10:27:06.627+01:00| modconfig| I125: Initialized! Lets do this thing…
    2018-02-13T10:27:06.627+01:00| modconfig| I125: Obtaining info using the running kernel.
    2018-02-13T10:27:06.627+01:00| modconfig| I125: Created new pathsHash.
    2018-02-13T10:27:06.627+01:00| modconfig| I125: Setting header path for 4.14.18-300.fc27.x86_64 to “/lib/modules/4.14.18-300.fc27.x86_64/build/include”.
    2018-02-13T10:27:06.627+01:00| modconfig| I125: Validating path “/lib/modules/4.14.18-300.fc27.x86_64/build/include” for kernel release “4.14.18-300.fc27.x86_64”.
    2018-02-13T10:27:06.629+01:00| modconfig| I125: Failed to find /lib/modules/4.14.18-300.fc27.x86_64/build/include/linux/version.h
    2018-02-13T10:27:06.629+01:00| modconfig| I125: /lib/modules/4.14.18-300.fc27.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
    2018-02-13T10:27:06.630+01:00| modconfig| I125: using /usr/bin/gcc for preprocess check
    2018-02-13T10:27:06.667+01:00| modconfig| I125: Preprocessed UTS_RELEASE, got value “4.14.18-300.fc27.x86_64”.
    2018-02-13T10:27:06.668+01:00| modconfig| I125: The header path “/lib/modules/4.14.18-300.fc27.x86_64/build/include” for the kernel “4.14.18-300.fc27.x86_64” is valid. Whoohoo!
    2018-02-13T10:27:06.765+01:00| modconfig| I125: found symbol version file /lib/modules/4.14.18-300.fc27.x86_64/build/Module.symvers
    2018-02-13T10:27:06.765+01:00| modconfig| I125: Reading symbol versions from /lib/modules/4.14.18-300.fc27.x86_64/build/Module.symvers.
    2018-02-13T10:27:06.778+01:00| modconfig| I125: Read 19135 symbol versions
    2018-02-13T10:27:06.778+01:00| modconfig| I125: Reading in info for the vmmon module.
    2018-02-13T10:27:06.778+01:00| modconfig| I125: Reading in info for the vmnet module.
    2018-02-13T10:27:06.778+01:00| modconfig| I125: Reading in info for the vmblock module.
    2018-02-13T10:27:06.778+01:00| modconfig| I125: Reading in info for the vmci module.
    2018-02-13T10:27:06.778+01:00| modconfig| I125: Reading in info for the vsock module.
    2018-02-13T10:27:06.778+01:00| modconfig| I125: Setting vsock to depend on vmci.
    2018-02-13T10:27:06.784+01:00| modconfig| I125: Trying to find a suitable PBM set for kernel “4.14.18-300.fc27.x86_64”.
    2018-02-13T10:27:06.784+01:00| modconfig| I125: No matching PBM set was found for kernel “4.14.18-300.fc27.x86_64”.
    2018-02-13T10:27:06.784+01:00| modconfig| I125: Found compiler at “/usr/bin/gcc”
    2018-02-13T10:27:06.786+01:00| modconfig| I125: Got gcc version “7”.
    2018-02-13T10:27:06.786+01:00| modconfig| I125: The GCC version matches the kernel GCC minor version like a glove.
    2018-02-13T10:27:06.786+01:00| modconfig| I125: Using temp dir “/tmp”.
    2018-02-13T10:27:06.811+01:00| modconfig| I125: Setting destination path for vmmon to “/lib/modules/4.14.18-300.fc27.x86_64/misc/vmmon.ko”.
    2018-02-13T10:27:06.811+01:00| modconfig| I125: Extracting the vmmon source from “/usr/lib/vmware/modules/source/vmmon.tar”.
    2018-02-13T10:27:06.815+01:00| modconfig| I125: Successfully extracted the vmmon source.
    2018-02-13T10:27:06.815+01:00| modconfig| I125: Building module with command “/usr/bin/make -j8 -C /tmp/modconfig-iRZI8G/vmmon-only auto-build HEADER_DIR=/lib/modules/4.14.18-300.fc27.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no”
    2018-02-13T10:27:07.555+01:00| modconfig| W115: Failed to build vmmon. Failed to execute the build command.
    2018-02-13T10:27:07.555+01:00| modconfig| I125: Setting destination path for vmnet to “/lib/modules/4.14.18-300.fc27.x86_64/misc/vmnet.ko”.
    2018-02-13T10:27:07.555+01:00| modconfig| I125: Extracting the vmnet source from “/usr/lib/vmware/modules/source/vmnet.tar”.
    2018-02-13T10:27:07.557+01:00| modconfig| I125: Successfully extracted the vmnet source.
    2018-02-13T10:27:07.557+01:00| modconfig| I125: Building module with command “/usr/bin/make -j8 -C /tmp/modconfig-iRZI8G/vmnet-only auto-build HEADER_DIR=/lib/modules/4.14.18-300.fc27.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no”
    2018-02-13T10:27:08.289+01:00| modconfig| W115: Failed to build vmnet. Failed to execute the build command.
    2018-02-13T10:27:08.293+01:00| modconfig| I125: We are now shutdown. Ready to die!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.