VMWare Workstation Pro 15 module compile errors on the latest update (20190314)

English Applications
1

VMware workstation pro will automatically prompt for compiling some of its modules and loading them into the running kernel every time it detects a kernel update. It would run for a short while and everything launches just fine afterwards.

However, today in the morning I did a distribution upgrade which brought up the Kernel to 5.0.1.1 and somehow the VMware module compile now fails compiling the Virtual Machine Monitor and the Virtual Network Device modules.

The failed process points to a rather lengthy log file for further details:

2019-03-16T11:45:49.011+03:30| host-21711| I125: Log for VMwa
re Workstation pid=21711 version=15.0.2 build=build-10952284 
option=Release
2019-03-16T11:45:49.011+03:30| host-21711| I125: The process 
is 64-bit.
2019-03-16T11:45:49.011+03:30| host-21711| I125: Host codepag
e=UTF-8 encoding=UTF-8
2019-03-16T11:45:49.011+03:30| host-21711| I125: Host is Linu
x 5.0.1-1-default openSUSE Tumbleweed
2019-03-16T11:45:49.011+03:30| host-21711| I125: DictionaryLo
ad: Cannot open file "/usr/lib/vmware/settings": No such file
 or directory.
2019-03-16T11:45:49.011+03:30| host-21711| I125: [msg.diction
ary.load.openFailed] Cannot open file "/usr/lib/vmware/settin
gs": No such file or directory.
2019-03-16T11:45:49.011+03:30| host-21711| I125: PREF Optiona
l preferences file not found at /usr/lib/vmware/settings. Usi
ng default values.
2019-03-16T11:45:49.011+03:30| host-21711| I125: DictionaryLo
ad: Cannot open file "/home/taker/.vmware/config": No such fi
le or directory.
2019-03-16T11:45:49.011+03:30| host-21711| I125: [msg.diction
ary.load.openFailed] Cannot open file "/home/taker/.vmware/co
nfig": No such file or directory.
2019-03-16T11:45:49.011+03:30| host-21711| I125: PREF Optiona
l preferences file not found at /home/taker/.vmware/config. U
sing default values.
2019-03-16T11:45:49.024+03:30| host-21711| W115: Logging to /
tmp/vmware-root/vmware-21711.log
2019-03-16T11:45:49.039+03:30| host-21711| I125: Obtaining in
fo using the running kernel.
2019-03-16T11:45:49.039+03:30| host-21711| I125: Created new 
pathsHash.
2019-03-16T11:45:49.039+03:30| host-21711| I125: Setting head
er path for 5.0.1-1-default to "/lib/modules/5.0.1-1-default/
build/include".
2019-03-16T11:45:49.039+03:30| host-21711| I125: Validating p
ath "/lib/modules/5.0.1-1-default/build/include" for kernel r
elease "5.0.1-1-default".
2019-03-16T11:45:49.039+03:30| host-21711| I125: Failed to fi
nd /lib/modules/5.0.1-1-default/build/include/linux/version.h
2019-03-16T11:45:49.039+03:30| host-21711| I125: /lib/modules
/5.0.1-1-default/build/include/linux/version.h not found, loo
king for generated/uapi/linux/version.h instead.
2019-03-16T11:45:49.039+03:30| host-21711| I125: using /usr/b
in/gcc-8 for preprocess check
2019-03-16T11:45:49.044+03:30| host-21711| I125: Preprocessed
 UTS_RELEASE, got value "5.0.1-1-default".
2019-03-16T11:45:49.044+03:30| host-21711| I125: The header p
ath "/lib/modules/5.0.1-1-default/build/include" for the kern
el "5.0.1-1-default" is valid.  Whoohoo!
2019-03-16T11:45:49.250+03:30| host-21711| I125: found symbol
 version file /lib/modules/5.0.1-1-default/build/Module.symve
rs
2019-03-16T11:45:49.250+03:30| host-21711| I125: Reading symb
ol versions from /lib/modules/5.0.1-1-default/build/Module.sy
mvers.
2019-03-16T11:45:49.273+03:30| host-21711| I125: Read 21303 s
ymbol versions
2019-03-16T11:45:49.273+03:30| host-21711| I125: Reading in i
nfo for the vmmon module.
2019-03-16T11:45:49.273+03:30| host-21711| I125: Reading in i
nfo for the vmnet module.
2019-03-16T11:45:49.273+03:30| host-21711| I125: Reading in i
nfo for the vmci module.
2019-03-16T11:45:49.273+03:30| host-21711| I125: Reading in i
nfo for the vsock module.
2019-03-16T11:45:49.273+03:30| host-21711| I125: Setting vsoc
k to depend on vmci.
2019-03-16T11:45:49.273+03:30| host-21711| I125: Invoking mod
info on "vmmon".
2019-03-16T11:45:49.275+03:30| host-21711| I125: "/sbin/modin
fo" exited with status 256.
2019-03-16T11:45:49.275+03:30| host-21711| I125: Invoking mod
info on "vmnet".
2019-03-16T11:45:49.276+03:30| host-21711| I125: "/sbin/modin
fo" exited with status 256.
2019-03-16T11:45:49.276+03:30| host-21711| I125: Invoking mod
info on "vmci".
2019-03-16T11:45:49.277+03:30| host-21711| I125: "/sbin/modin
fo" exited with status 256.
2019-03-16T11:45:49.277+03:30| host-21711| I125: Invoking mod
info on "vsock".
2019-03-16T11:45:49.279+03:30| host-21711| I125: "/sbin/modin
fo" exited with status 0.
2019-03-16T11:45:49.293+03:30| host-21711| I125: to be instal
led: vmmon status: 0
2019-03-16T11:45:49.293+03:30| host-21711| I125: to be instal
led: vmnet status: 0
2019-03-16T11:45:49.336+03:30| host-21711| I125: Obtaining in
fo using the running kernel.
2019-03-16T11:45:49.336+03:30| host-21711| I125: Setting head
er path for 5.0.1-1-default to "/lib/modules/5.0.1-1-default/
build/include".
2019-03-16T11:45:49.336+03:30| host-21711| I125: Validating p
ath "/lib/modules/5.0.1-1-default/build/include" for kernel r
elease "5.0.1-1-default".
2019-03-16T11:45:49.336+03:30| host-21711| I125: Failed to fi
nd /lib/modules/5.0.1-1-default/build/include/linux/version.h
2019-03-16T11:45:49.336+03:30| host-21711| I125: /lib/modules
/5.0.1-1-default/build/include/linux/version.h not found, loo
king for generated/uapi/linux/version.h instead.
2019-03-16T11:45:49.336+03:30| host-21711| I125: using /usr/b
in/gcc-8 for preprocess check
2019-03-16T11:45:49.341+03:30| host-21711| I125: Preprocessed
 UTS_RELEASE, got value "5.0.1-1-default".
2019-03-16T11:45:49.341+03:30| host-21711| I125: The header p
ath "/lib/modules/5.0.1-1-default/build/include" for the kern
el "5.0.1-1-default" is valid.  Whoohoo!
2019-03-16T11:45:49.545+03:30| host-21711| I125: found symbol
 version file /lib/modules/5.0.1-1-default/build/Module.symve
rs
2019-03-16T11:45:49.545+03:30| host-21711| I125: Reading symb
ol versions from /lib/modules/5.0.1-1-default/build/Module.sy
mvers.
2019-03-16T11:45:49.567+03:30| host-21711| I125: Read 21303 s
ymbol versions
2019-03-16T11:45:49.568+03:30| host-21711| I125: Kernel heade
r path retrieved from FileEntry: /lib/modules/5.0.1-1-default
/build/include
2019-03-16T11:45:49.568+03:30| host-21711| I125: Update kerne
l header path to /lib/modules/5.0.1-1-default/build/include
2019-03-16T11:45:49.568+03:30| host-21711| I125: Validating p
ath "/lib/modules/5.0.1-1-default/build/include" for kernel r
elease "5.0.1-1-default".
2019-03-16T11:45:49.568+03:30| host-21711| I125: Failed to fi
nd /lib/modules/5.0.1-1-default/build/include/linux/version.h
2019-03-16T11:45:49.568+03:30| host-21711| I125: /lib/modules
/5.0.1-1-default/build/include/linux/version.h not found, loo
king for generated/uapi/linux/version.h instead.
2019-03-16T11:45:49.568+03:30| host-21711| I125: using /usr/b
in/gcc-8 for preprocess check
2019-03-16T11:45:49.573+03:30| host-21711| I125: Preprocessed
 UTS_RELEASE, got value "5.0.1-1-default".
2019-03-16T11:45:49.573+03:30| host-21711| I125: The header p
ath "/lib/modules/5.0.1-1-default/build/include" for the kern
el "5.0.1-1-default" is valid.  Whoohoo!
2019-03-16T11:45:49.575+03:30| host-21711| I125: Found compil
er at "/usr/bin/gcc"
2019-03-16T11:45:49.577+03:30| host-21711| I125: Got gcc vers
ion "8".
2019-03-16T11:45:49.577+03:30| host-21711| I125: The GCC vers
ion matches the kernel GCC minor version like a glove.
2019-03-16T11:45:49.579+03:30| host-21711| I125: Got gcc vers
ion "8".
2019-03-16T11:45:49.579+03:30| host-21711| I125: The GCC vers
ion matches the kernel GCC minor version like a glove.
2019-03-16T11:45:49.580+03:30| host-21711| I125: Trying to fi
nd a suitable PBM set for kernel "5.0.1-1-default".
2019-03-16T11:45:49.580+03:30| host-21711| I125: No matching 
PBM set was found for kernel "5.0.1-1-default".
2019-03-16T11:45:49.580+03:30| host-21711| I125: The GCC vers
ion matches the kernel GCC minor version like a glove.
2019-03-16T11:45:49.580+03:30| host-21711| I125: Validating p
ath "/lib/modules/5.0.1-1-default/build/include" for kernel r
elease "5.0.1-1-default".
2019-03-16T11:45:49.580+03:30| host-21711| I125: Failed to fi
nd /lib/modules/5.0.1-1-default/build/include/linux/version.h
2019-03-16T11:45:49.580+03:30| host-21711| I125: /lib/modules
/5.0.1-1-default/build/include/linux/version.h not found, loo
king for generated/uapi/linux/version.h instead.
2019-03-16T11:45:49.580+03:30| host-21711| I125: using /usr/b
in/gcc-8 for preprocess check
2019-03-16T11:45:49.585+03:30| host-21711| I125: Preprocessed
 UTS_RELEASE, got value "5.0.1-1-default".
2019-03-16T11:45:49.585+03:30| host-21711| I125: The header p
ath "/lib/modules/5.0.1-1-default/build/include" for the kern
el "5.0.1-1-default" is valid.  Whoohoo!
2019-03-16T11:45:49.585+03:30| host-21711| I125: The GCC vers
ion matches the kernel GCC minor version like a glove.
2019-03-16T11:45:49.585+03:30| host-21711| I125: Validating p
ath "/lib/modules/5.0.1-1-default/build/include" for kernel r
elease "5.0.1-1-default".
2019-03-16T11:45:49.585+03:30| host-21711| I125: Failed to fi
nd /lib/modules/5.0.1-1-default/build/include/linux/version.h
2019-03-16T11:45:49.585+03:30| host-21711| I125: /lib/modules
/5.0.1-1-default/build/include/linux/version.h not found, loo
king for generated/uapi/linux/version.h instead.
2019-03-16T11:45:49.586+03:30| host-21711| I125: using /usr/b
in/gcc-8 for preprocess check
2019-03-16T11:45:49.590+03:30| host-21711| I125: Preprocessed
 UTS_RELEASE, got value "5.0.1-1-default".
2019-03-16T11:45:49.590+03:30| host-21711| I125: The header p
ath "/lib/modules/5.0.1-1-default/build/include" for the kern
el "5.0.1-1-default" is valid.  Whoohoo!
2019-03-16T11:45:49.590+03:30| host-21711| I125: Using temp d
ir "/tmp".
2019-03-16T11:45:49.593+03:30| host-21711| I125: Obtaining in
fo using the running kernel.
2019-03-16T11:45:49.593+03:30| host-21711| I125: Setting head
er path for 5.0.1-1-default to "/lib/modules/5.0.1-1-default/
build/include".
2019-03-16T11:45:49.593+03:30| host-21711| I125: Validating p
ath "/lib/modules/5.0.1-1-default/build/include" for kernel r
elease "5.0.1-1-default".
2019-03-16T11:45:49.593+03:30| host-21711| I125: Failed to fi
nd /lib/modules/5.0.1-1-default/build/include/linux/version.h
2019-03-16T11:45:49.593+03:30| host-21711| I125: /lib/modules
/5.0.1-1-default/build/include/linux/version.h not found, loo
king for generated/uapi/linux/version.h instead.
2019-03-16T11:45:49.593+03:30| host-21711| I125: using /usr/b
in/gcc-8 for preprocess check
2019-03-16T11:45:49.598+03:30| host-21711| I125: Preprocessed
 UTS_RELEASE, got value "5.0.1-1-default".
2019-03-16T11:45:49.598+03:30| host-21711| I125: The header p
ath "/lib/modules/5.0.1-1-default/build/include" for the kern
el "5.0.1-1-default" is valid.  Whoohoo!
2019-03-16T11:45:49.804+03:30| host-21711| I125: found symbol
 version file /lib/modules/5.0.1-1-default/build/Module.symve
rs
2019-03-16T11:45:49.804+03:30| host-21711| I125: Reading symb
ol versions from /lib/modules/5.0.1-1-default/build/Module.sy
mvers.
2019-03-16T11:45:49.827+03:30| host-21711| I125: Read 21303 s
ymbol versions
2019-03-16T11:45:49.827+03:30| host-21711| I125: Invoking mod
info on "vmmon".
2019-03-16T11:45:49.829+03:30| host-21711| I125: "/sbin/modin
fo" exited with status 256.
2019-03-16T11:45:49.830+03:30| host-21711| I125: Invoking mod
info on "vmnet".
2019-03-16T11:45:49.831+03:30| host-21711| I125: "/sbin/modin
fo" exited with status 256.
2019-03-16T11:45:50.618+03:30| host-21711| I125: Setting dest
ination path for vmmon to "/lib/modules/5.0.1-1-default/misc/
vmmon.ko".
2019-03-16T11:45:50.619+03:30| host-21711| I125: Extracting t
he vmmon source from "/usr/lib/vmware/modules/source/vmmon.ta
r".
2019-03-16T11:45:50.626+03:30| host-21711| I125: Successfully
 extracted the vmmon source.
2019-03-16T11:45:50.626+03:30| host-21711| I125: Building mod
ule with command "/usr/bin/make -j8 -C /tmp/modconfig-zaD5AZ/
vmmon-only auto-build HEADER_DIR=/lib/modules/5.0.1-1-default
/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2019-03-16T11:45:52.722+03:30| host-21711| W115: Failed to bu
ild vmmon.  Failed to execute the build command.
2019-03-16T11:45:52.724+03:30| host-21711| I125: Setting dest
ination path for vmnet to "/lib/modules/5.0.1-1-default/misc/
vmnet.ko".
2019-03-16T11:45:52.724+03:30| host-21711| I125: Extracting t
he vmnet source from "/usr/lib/vmware/modules/source/vmnet.ta
r".
2019-03-16T11:45:52.729+03:30| host-21711| I125: Successfully
 extracted the vmnet source.
2019-03-16T11:45:52.729+03:30| host-21711| I125: Building mod
ule with command "/usr/bin/make -j8 -C /tmp/modconfig-zaD5AZ/
vmnet-only auto-build HEADER_DIR=/lib/modules/5.0.1-1-default
/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2019-03-16T11:45:55.183+03:30| host-21711| W115: Failed to bu
ild vmnet.  Failed to execute the build command.

I haven’t changed anything else in the system or removed any files from their previous locations from earlier before when I made the upgrade.

Badly need my VMs and so any help is much appreciated.

Cheers.

2

I did some more Googling trying to fix this and wanted to update the community on my discoveries even though I did not manage to actually fix it yet.

  • I completely removed my installation of the VMWare Workstation Pro (15.0.1) and downloaded and installed the latest version (15.0.3) hoping for a fix but to no avail.
  • Since I needed to work with my VMs and could not find the work around despite what tried I booted into my snapper snapshot which was automatically made before the distribution update which confirmed my earlier suspicion. VMWare pops up and works flawlessly under the previous kernel 4.20.13.1.

So I can confirm that whatever it is that caused the issue rests in the 20190314 update and the 5.0.1.1 Kernel. for the time being I rolled back to be able to get some work done with my VMs but I would very much like a resolution to this issue going forward.

Cheers.

3

Hi
You would need to look at following up with the Third party eg VMware (Support Request), I would also check their forums as someone may have provided a patch…

4

Although your log doesn’t state any specific cause for your building vmon error,
historically the most common reason for failures on TW is because the default gcc is too new and not yet fully supported.

I’d recommend you install gcc7,
Then configure your system for gcc7 uisng Update Alternatives which I describe in my Wiki article

https://en.opensuse.org/User:Tsu2/gcc_update-alternatives

Then, execute your VMware workstation build script as you’ve already done.
Afterwarrds, you can leave your system set to gcc7 or switch back to gcc8, gcc is run only when building something and isn’t invoked for any ordinary and common use. Of course, you might have to remember what your gcc setting.

Note that if you had posted in the Virtualization forum which is more specific than this Applications forum, you’d have gotten better eyeballs on your issue and if you had searched that forum, depending on your search parameters you might have found those posts for previous versions of Workstation which had install problems.

HTH,
TSU

5

On Mon 18 Mar 2019 02:46:03 PM CDT, tsu2 wrote:

Although your log doesn’t state any specific cause for your building
vmon error,
historically the most common reason for failures on TW is because the
default gcc is too new and not yet fully supported.

I’d recommend you install gcc7,
Then configure your system for gcc7 uisng Update Alternatives which I
describe in my Wiki article

User:Tsu2/gcc update-alternatives - openSUSE Wiki

Then, execute your VMware workstation build script as you’ve already
done.
Afterwarrds, you can leave your system set to gcc7 or switch back to
gcc8, gcc is run only when building something and isn’t invoked for any
ordinary and common use. Of course, you might have to remember what your
gcc setting.

Note that if you had posted in the Virtualization forum which is more
specific than this Applications forum, you’d have gotten better eyeballs
on your issue and if you had searched that forum, depending on your
search parameters you might have found those posts for previous versions
of Workstation which had install problems.

HTH,
TSU

Hi
No it’s not, as indicated patches are required for the kernel changes
in moving to 5.x kernel.

See: Re: [opensuse-factory] vmware player does not build on kernel 5.0.1 Was: New Tumbleweed snapshot 20190314 released! - openSUSE Factory - openSUSE Mailing Lists

Please don’t use a different version of gcc…

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.28-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

6

So,
I suppose then that you’re saying that the User has little choice but to revert to a 4.x kernel running Workstation (or likely any VMware product and possibly other apps which require building kernel modules). This also appears to break a fairly standard policy nearly everyone including kernel development to always support the most recent past version and never introduce something so new without at least a little backwards compatibility that will guarantee breakage.

I don’t know if this appears to be a problem App vendors can address in a timely manner, particularly for a Dev type rolling release like TW…

TSU

7

Hi
Well it’s always an issue with third party components, eg Nvidia, Virtualbox, vmware when kernel changes occur… in this case AFAIK it’s a $$ product, head off to their support for a fix? Else consider learning how to create patches (or check the 3rd party forums) for any patches necessary and how to apply for a particular driver. Once you have done it a few times it’s not that bad…

To be honest I’m sure third party vendors can (and do) work with later kernels before release, just a matter of finding out the place to look, which in most cases is their support forums.

8

AFAIK VMware Workstation 15 is only about a month old,
And VMware has a pretty consistent record over time for not supporting new kernels the moment TW deploys… In rare cases have released the fix within a month but often takes much longer than that.

The standard fix in the past has been to compile with an older gcc as I described, if that’s not possible then recommend downgrading the kernel and check with VMware periodiodically (or set the Workstation updates to notify you once an update is pending).

TSU

9

Hi
Which ultimately invalidates the use of Tumbleweed in this use case? All the more reason to avoid third party products and look at moving to the oss solutions…

10

Hi
And a quick search turns up http://rglinuxtech.com/?cat=1533 (patches for 5.0 have been available since January) and look at http://rglinuxtech.com/?p=2477 which points to one of the SUSE folks git repository GitHub - mkubecek/vmware-host-modules: Patches needed to build VMware (Player and Workstation) host modules against recent kernels check the releases tab… This person also is present in the Factory mailing list thread I posted…