VMware Communities
xsdenied
Contributor
Contributor
Jump to solution

After fedora 29 upgrades kernel 5.0.3-200.fc29.x86_64 vmmon and vmnet are not building

Hi,

After upgrading fedora 29 to 5.0.3-200.fc29.x86_64 i can not start vmware workstation pro, tried uninstalling and reinstalling no success using (VMware-Workstation-Full-15.0.3-12422535.x86_64.bundle). Any one has a suggestion?

2019-03-27T10:51:11.984+03:00| host-9907| I125: Log for VMware Workstation pid=9907 version=15.0.3 build=build-12422535 option=Release

2019-03-27T10:51:11.984+03:00| host-9907| I125: The process is 64-bit.

2019-03-27T10:51:11.984+03:00| host-9907| I125: Host codepage=UTF-8 encoding=UTF-8

2019-03-27T10:51:11.984+03:00| host-9907| I125: Host is Linux 5.0.3-200.fc29.x86_64 Fedora release 29 (Twenty Nine)

2019-03-27T10:51:11.984+03:00| host-9907| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2019-03-27T10:51:11.984+03:00| host-9907| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2019-03-27T10:51:11.984+03:00| host-9907| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2019-03-27T10:51:11.984+03:00| host-9907| I125: DictionaryLoad: Cannot open file "/home/ismet/.vmware/config": No such file or directory.

2019-03-27T10:51:11.984+03:00| host-9907| I125: [msg.dictionary.load.openFailed] Cannot open file "/home/ismet/.vmware/config": No such file or directory.

2019-03-27T10:51:11.984+03:00| host-9907| I125: PREF Optional preferences file not found at /home/ismet/.vmware/config. Using default values.

2019-03-27T10:51:11.991+03:00| host-9907| W115: Logging to /tmp/vmware-root/vmware-9907.log

2019-03-27T10:51:11.996+03:00| host-9907| I125: Obtaining info using the running kernel.

2019-03-27T10:51:11.996+03:00| host-9907| I125: Created new pathsHash.

2019-03-27T10:51:11.996+03:00| host-9907| I125: Setting header path for 5.0.3-200.fc29.x86_64 to "/lib/modules/5.0.3-200.fc29.x86_64/build/include".

2019-03-27T10:51:11.996+03:00| host-9907| I125: Validating path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for kernel release "5.0.3-200.fc29.x86_64".

2019-03-27T10:51:11.996+03:00| host-9907| I125: Failed to find /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h

2019-03-27T10:51:11.996+03:00| host-9907| I125: /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-03-27T10:51:11.996+03:00| host-9907| I125: using /usr/bin/gcc for preprocess check

2019-03-27T10:51:12.000+03:00| host-9907| I125: Preprocessed UTS_RELEASE, got value "5.0.3-200.fc29.x86_64".

2019-03-27T10:51:12.000+03:00| host-9907| I125: The header path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for the kernel "5.0.3-200.fc29.x86_64" is valid.  Whoohoo!

2019-03-27T10:51:12.112+03:00| host-9907| I125: found symbol version file /lib/modules/5.0.3-200.fc29.x86_64/build/Module.symvers

2019-03-27T10:51:12.112+03:00| host-9907| I125: Reading symbol versions from /lib/modules/5.0.3-200.fc29.x86_64/build/Module.symvers.

2019-03-27T10:51:12.122+03:00| host-9907| I125: Read 20627 symbol versions

2019-03-27T10:51:12.122+03:00| host-9907| I125: Reading in info for the vmmon module.

2019-03-27T10:51:12.122+03:00| host-9907| I125: Reading in info for the vmnet module.

2019-03-27T10:51:12.122+03:00| host-9907| I125: Reading in info for the vmci module.

2019-03-27T10:51:12.122+03:00| host-9907| I125: Reading in info for the vsock module.

2019-03-27T10:51:12.122+03:00| host-9907| I125: Setting vsock to depend on vmci.

2019-03-27T10:51:12.122+03:00| host-9907| I125: Invoking modinfo on "vmmon".

2019-03-27T10:51:12.124+03:00| host-9907| I125: "/sbin/modinfo" exited with status 256.

2019-03-27T10:51:12.124+03:00| host-9907| I125: Invoking modinfo on "vmnet".

2019-03-27T10:51:12.125+03:00| host-9907| I125: "/sbin/modinfo" exited with status 256.

2019-03-27T10:51:12.125+03:00| host-9907| I125: Invoking modinfo on "vmci".

2019-03-27T10:51:12.125+03:00| host-9907| I125: "/sbin/modinfo" exited with status 256.

2019-03-27T10:51:12.125+03:00| host-9907| I125: Invoking modinfo on "vsock".

2019-03-27T10:51:12.127+03:00| host-9907| I125: "/sbin/modinfo" exited with status 0.

2019-03-27T10:51:12.133+03:00| host-9907| I125: to be installed: vmmon status: 0

2019-03-27T10:51:12.133+03:00| host-9907| I125: to be installed: vmnet status: 0

2019-03-27T10:51:12.140+03:00| host-9907| I125: Obtaining info using the running kernel.

2019-03-27T10:51:12.140+03:00| host-9907| I125: Setting header path for 5.0.3-200.fc29.x86_64 to "/lib/modules/5.0.3-200.fc29.x86_64/build/include".

2019-03-27T10:51:12.140+03:00| host-9907| I125: Validating path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for kernel release "5.0.3-200.fc29.x86_64".

2019-03-27T10:51:12.140+03:00| host-9907| I125: Failed to find /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h

2019-03-27T10:51:12.140+03:00| host-9907| I125: /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-03-27T10:51:12.140+03:00| host-9907| I125: using /usr/bin/gcc for preprocess check

2019-03-27T10:51:12.143+03:00| host-9907| I125: Preprocessed UTS_RELEASE, got value "5.0.3-200.fc29.x86_64".

2019-03-27T10:51:12.143+03:00| host-9907| I125: The header path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for the kernel "5.0.3-200.fc29.x86_64" is valid.  Whoohoo!

2019-03-27T10:51:12.253+03:00| host-9907| I125: found symbol version file /lib/modules/5.0.3-200.fc29.x86_64/build/Module.symvers

2019-03-27T10:51:12.253+03:00| host-9907| I125: Reading symbol versions from /lib/modules/5.0.3-200.fc29.x86_64/build/Module.symvers.

2019-03-27T10:51:12.263+03:00| host-9907| I125: Read 20627 symbol versions

2019-03-27T10:51:12.263+03:00| host-9907| I125: Kernel header path retrieved from FileEntry: /lib/modules/5.0.3-200.fc29.x86_64/build/include

2019-03-27T10:51:12.263+03:00| host-9907| I125: Update kernel header path to /lib/modules/5.0.3-200.fc29.x86_64/build/include

2019-03-27T10:51:12.263+03:00| host-9907| I125: Validating path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for kernel release "5.0.3-200.fc29.x86_64".

2019-03-27T10:51:12.263+03:00| host-9907| I125: Failed to find /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h

2019-03-27T10:51:12.263+03:00| host-9907| I125: /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-03-27T10:51:12.263+03:00| host-9907| I125: using /usr/bin/gcc for preprocess check

2019-03-27T10:51:12.267+03:00| host-9907| I125: Preprocessed UTS_RELEASE, got value "5.0.3-200.fc29.x86_64".

2019-03-27T10:51:12.267+03:00| host-9907| I125: The header path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for the kernel "5.0.3-200.fc29.x86_64" is valid.  Whoohoo!

2019-03-27T10:51:12.268+03:00| host-9907| I125: Found compiler at "/usr/bin/gcc"

2019-03-27T10:51:12.269+03:00| host-9907| I125: Got gcc version "8".

2019-03-27T10:51:12.269+03:00| host-9907| I125: The GCC version matches the kernel GCC minor version like a glove.

2019-03-27T10:51:12.271+03:00| host-9907| I125: Got gcc version "8".

2019-03-27T10:51:12.271+03:00| host-9907| I125: The GCC version matches the kernel GCC minor version like a glove.

2019-03-27T10:51:12.272+03:00| host-9907| I125: Trying to find a suitable PBM set for kernel "5.0.3-200.fc29.x86_64".

2019-03-27T10:51:12.272+03:00| host-9907| I125: No matching PBM set was found for kernel "5.0.3-200.fc29.x86_64".

2019-03-27T10:51:12.276+03:00| host-9907| I125: Got gcc version "8".

2019-03-27T10:51:12.276+03:00| host-9907| I125: The GCC version matches the kernel GCC minor version like a glove.

2019-03-27T10:51:12.276+03:00| host-9907| I125: The GCC version matches the kernel GCC minor version like a glove.

2019-03-27T10:51:12.276+03:00| host-9907| I125: Validating path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for kernel release "5.0.3-200.fc29.x86_64".

2019-03-27T10:51:12.276+03:00| host-9907| I125: Failed to find /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h

2019-03-27T10:51:12.276+03:00| host-9907| I125: /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-03-27T10:51:12.276+03:00| host-9907| I125: using /usr/bin/gcc for preprocess check

2019-03-27T10:51:12.279+03:00| host-9907| I125: Preprocessed UTS_RELEASE, got value "5.0.3-200.fc29.x86_64".

2019-03-27T10:51:12.279+03:00| host-9907| I125: The header path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for the kernel "5.0.3-200.fc29.x86_64" is valid.  Whoohoo!

2019-03-27T10:51:12.280+03:00| host-9907| I125: The GCC version matches the kernel GCC minor version like a glove.

2019-03-27T10:51:12.280+03:00| host-9907| I125: Validating path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for kernel release "5.0.3-200.fc29.x86_64".

2019-03-27T10:51:12.280+03:00| host-9907| I125: Failed to find /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h

2019-03-27T10:51:12.280+03:00| host-9907| I125: /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-03-27T10:51:12.280+03:00| host-9907| I125: using /usr/bin/gcc for preprocess check

2019-03-27T10:51:12.283+03:00| host-9907| I125: Preprocessed UTS_RELEASE, got value "5.0.3-200.fc29.x86_64".

2019-03-27T10:51:12.283+03:00| host-9907| I125: The header path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for the kernel "5.0.3-200.fc29.x86_64" is valid.  Whoohoo!

2019-03-27T10:51:12.283+03:00| host-9907| I125: Using temp dir "/tmp".

2019-03-27T10:51:12.284+03:00| host-9907| I125: Obtaining info using the running kernel.

2019-03-27T10:51:12.284+03:00| host-9907| I125: Setting header path for 5.0.3-200.fc29.x86_64 to "/lib/modules/5.0.3-200.fc29.x86_64/build/include".

2019-03-27T10:51:12.284+03:00| host-9907| I125: Validating path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for kernel release "5.0.3-200.fc29.x86_64".

2019-03-27T10:51:12.284+03:00| host-9907| I125: Failed to find /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h

2019-03-27T10:51:12.284+03:00| host-9907| I125: /lib/modules/5.0.3-200.fc29.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-03-27T10:51:12.284+03:00| host-9907| I125: using /usr/bin/gcc for preprocess check

2019-03-27T10:51:12.288+03:00| host-9907| I125: Preprocessed UTS_RELEASE, got value "5.0.3-200.fc29.x86_64".

2019-03-27T10:51:12.288+03:00| host-9907| I125: The header path "/lib/modules/5.0.3-200.fc29.x86_64/build/include" for the kernel "5.0.3-200.fc29.x86_64" is valid.  Whoohoo!

2019-03-27T10:51:12.400+03:00| host-9907| I125: found symbol version file /lib/modules/5.0.3-200.fc29.x86_64/build/Module.symvers

2019-03-27T10:51:12.400+03:00| host-9907| I125: Reading symbol versions from /lib/modules/5.0.3-200.fc29.x86_64/build/Module.symvers.

2019-03-27T10:51:12.410+03:00| host-9907| I125: Read 20627 symbol versions

2019-03-27T10:51:12.410+03:00| host-9907| I125: Invoking modinfo on "vmmon".

2019-03-27T10:51:12.412+03:00| host-9907| I125: "/sbin/modinfo" exited with status 256.

2019-03-27T10:51:12.412+03:00| host-9907| I125: Invoking modinfo on "vmnet".

2019-03-27T10:51:12.413+03:00| host-9907| I125: "/sbin/modinfo" exited with status 256.

2019-03-27T10:51:12.461+03:00| host-9907| I125: Setting destination path for vmmon to "/lib/modules/5.0.3-200.fc29.x86_64/misc/vmmon.ko".

2019-03-27T10:51:12.462+03:00| host-9907| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2019-03-27T10:51:12.466+03:00| host-9907| I125: Successfully extracted the vmmon source.

2019-03-27T10:51:12.466+03:00| host-9907| I125: Building module with command "/usr/bin/make -j16 -C /tmp/modconfig-1d9cBn/vmmon-only auto-build HEADER_DIR=/lib/modules/5.0.3-200.fc29.x86_64/build/include CC=/usr/lib64/ccache/gcc IS_GCC_3=no"

2019-03-27T10:51:13.512+03:00| host-9907| W115: Failed to build vmmon.  Failed to execute the build command.

2019-03-27T10:51:13.513+03:00| host-9907| I125: Setting destination path for vmnet to "/lib/modules/5.0.3-200.fc29.x86_64/misc/vmnet.ko".

2019-03-27T10:51:13.513+03:00| host-9907| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

2019-03-27T10:51:13.516+03:00| host-9907| I125: Successfully extracted the vmnet source.

2019-03-27T10:51:13.516+03:00| host-9907| I125: Building module with command "/usr/bin/make -j16 -C /tmp/modconfig-1d9cBn/vmnet-only auto-build HEADER_DIR=/lib/modules/5.0.3-200.fc29.x86_64/build/include CC=/usr/lib64/ccache/gcc IS_GCC_3=no"

2019-03-27T10:51:15.047+03:00| host-9907| W115: Failed to build vmnet.  Failed to execute the build command.

1 Solution

Accepted Solutions
mfelker
Expert
Expert
Jump to solution

Try one of these patches  by the author @mkubecek.

https://github.com/mkubecek/vmware-host-modules

View solution in original post

Reply
0 Kudos
15 Replies
mfelker
Expert
Expert
Jump to solution

Try one of these patches  by the author @mkubecek.

https://github.com/mkubecek/vmware-host-modules

Reply
0 Kudos
noldis
Contributor
Contributor
Jump to solution

Even WS Pro 15.0.4 doesn't work with kernel 5.0.3.

VMware, please fix your code so that we can move on!

Br, Arnold

mkubecek
Hot Shot
Hot Shot
Jump to solution

That's not surprising, the host module sources haven't changed since 15.0.1, all later releases only fixed some serious bugs. In a simiar fashion, versions 14.1.3 through 14.1.7 also have the same host modules.

Reply
0 Kudos
crorion
Contributor
Contributor
Jump to solution

Same thing here!

2019-03-31T23:49:44.967-06:00| host-29483| I125: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-PYtwuj/vmnet-only auto-build HEADER_DIR=/lib/modules/5.0.4-200.fc29.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2019-03-31T23:49:46.463-06:00| host-29483| W115: Failed to build vmnet.  Failed to execute the build command.

I haven´t attempted any of the patches yet, if I get some time I might just give it a go. Mainly posting so that they know the issue is affecting a significant number of Linux users.

RDPetruska
Leadership
Leadership
Jump to solution

Even WS Pro 15.0.4 doesn't work with kernel 5.0.3.

VMware, please fix your code so that we can move on!

Please realize that Fedora is NOT a Supported Host OS!  Therefore, VMware will be spending resources on Supported host OS's first.  Fedora may work, but may require 3rd party patches such as mentioned in the previous post.

Reply
0 Kudos
noldis
Contributor
Contributor
Jump to solution

Hi RDPetruska,

I fully agree that VMware workstation can not do everything for everybody. Resources are limited and demand is rampant.

Nevertheless, I think this case is different: Linux kernel 5.0 are popping up all over the place now and VMware has to do it anyway for WS and all other hypervisor products, so  why not fix the code sooner than later. We are not asking installer / handling questions (although I would if I had any!-) but fundamental stuff.

If you tell me that it won't happen till WS 16 then we will certainly look into the patches supplied by mkubecek but if VMware fixes it soon, then it won't be worth it and we'd rather stay with the original supplier's code.

Thanks for listening!

Reply
0 Kudos
mkubecek
Hot Shot
Hot Shot
Jump to solution

Unlike others, I don't blame VMware for not having fixed the build against 5.0 kernel yet (even if I have pretty good idea how "immense" amount of work would it require). I get it, it's a big company, there are processes and policies and last three point releases were only quick fixes for specific bugs. If you want to run Workstation/Player on a host with recent kernel, there is an easy way around it. What I find more disturbing is the growing list of build warnings (oldest showing since mainline 4.9, i.e. December 2016), including one unprotected indirect call, which doesn't seem to bother VMware developers at all.

Reply
0 Kudos
ALBentleyIII
Contributor
Contributor
Jump to solution

slight correction.  Fedora 28 is supported, Fedora 29 is not.

Reply
0 Kudos
RDPetruska
Leadership
Leadership
Jump to solution

My mistake, reading the release notes, Fedora 29 was added as a Supported guest AND host OS in Workstation 15.01.  I remember in earlier versions of Workstation, Fedora was not a Supported host OS, only a guest OS.  Sorry for the misinformation.

Well, then I can only guess that the VMware developers are working on official support for the new Kernel 5.0x.  Employees cannot comment on future releases.

Reply
0 Kudos
xsdenied
Contributor
Contributor
Jump to solution

I can confirm vmware-host-modules-w15.0.4-k5.0.tar.gz works on kernel 5.0.5-200.fc29.x86_64 with vmware workstation 15.0.4 build-12990004

Reply
0 Kudos
crorion
Contributor
Contributor
Jump to solution

Works indeed! Just go to the link below and follow the install instructions to replace the old modules with the built tarballs.

https://github.com/mkubecek/vmware-host-modules/archive/w15.0.4-k5.0.tar.gz

Reply
0 Kudos
kaengo
Enthusiast
Enthusiast
Jump to solution

Hello

kernel 5.0.1-1.el7.elrepo.x86_64 on CentOS 7.6.

(I think, it is the same problem, so I didn't start a new thread.)

I tried first to get my workstation player 15.0.2 working  ( it stopped after kernel update)

after that I tried to install a fresh workstation player 15.0.4.

I get both times the same result:

I tried the patch from mkubecek.

-----------------------------------------------------------------------------------------------------------------------------

First method of  installation breaks with error:

[holger@kraehe vmware-host-modules-workstation-15.0.2]$ make

make -C vmmon-only

Using kernel build system.

make[1]: Entering directory `/home/lokalinstaller/vmwareplayer/patch_kubecek/vmware-host-modules-workstation-15.0.2/vmmon-only'

make -C /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include/.. M=$PWD SRCROOT=PWD/. \

  MODULEBUILDDIR= modules

make[2]: Entering directory `/usr/src/kernels/5.0.1-1.el7.elrepo.x86_64'

  CC [M]  /home/lokalinstaller/vmwareplayer/patch_kubecek/vmware-host-modules-wrkstation-15.0.2/vmmon-only/common/task.o

/home/lokalinstaller/vmwareplayer/patch_kubecek/vmware-host-modules-workstation15.0.2/vmmon-only/common/task.c: In function ‘Task_Switch’:

/home/lokalinstaller/vmwareplayer/patch_kubecek/vmware-host-modules-workstation15.0.2/vmmon-only/common/task.c:2326:7: error: invalid 'asm': invalid operand cde 'V'

       __asm__ __volatile__(CALL_NOSPEC

       ^

make[3]: *** [/home/lokalinstaller/vmwareplayer/patch_kubecek/vmware-host-moduls-workstation-15.0.2/vmmon-only/common/task.o] Error 1

make[2]: *** [_module_/home/lokalinstaller/vmwareplayer/patch_kubecek/vmware-hot-modules-workstation-15.0.2/vmmon-only] Error 2

make[2]: Leaving directory `/usr/src/kernels/5.0.1-1.el7.elrepo.x86_64'

make[1]: *** [vmmon.ko] Error 2

make[1]: Leaving directory `/home/lokalinstaller/vmwareplayer/patch_kubecek/vmwre-host-modules-workstation-15.0.2/vmmon-only'

make: *** [vmmon-only] Error 2

[holger@kraehe vmware-host-modules-workstation-15.0.2]$

----------------------------------------------------------------------------------------------------------------------------------------

Second method gives also some errors:

-modules-workstation-15.0.2]$ su

Password:

ABRT has detected 1 problem(s). For more info run: abrt-cli list --since 1554327275

[root@kraehe vmware-host-modules-workstation-15.0.2]# cp -v vmmon.tar vmnet.tar /usr/lib/vmware/modules/source/

cp: overwrite ‘/usr/lib/vmware/modules/source/vmmon.tar’? y

‘vmmon.tar’ -> ‘/usr/lib/vmware/modules/source/vmmon.tar’

cp: overwrite ‘/usr/lib/vmware/modules/source/vmnet.tar’? y

‘vmnet.tar’ -> ‘/usr/lib/vmware/modules/source/vmnet.tar’

[root@kraehe vmware-host-modules-workstation-15.0.2]# vmware-modconfig --console --install-all

[AppLoader] GLib does not have GSettings support.

Stopping vmware (via systemctl):                           [  OK  ]

Using kernel build system.

make: Entering directory `/tmp/modconfig-dY8Xnm/vmmon-only'

/usr/bin/make -C /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include/.. M=$PWD SRCROOT=$PWD/. \

  MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/5.0.1-1.el7.elrepo.x86_64'

  CC [M]  /tmp/modconfig-dY8Xnm/vmmon-only/linux/hostif.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmmon-only/linux/driverLog.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmmon-only/linux/driver.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmmon-only/common/memtrack.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmmon-only/common/apic.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmmon-only/common/vmx86.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmmon-only/common/task.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmmon-only/common/cpuid.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmmon-only/common/comport.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmmon-only/common/phystrack.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmmon-only/vmcore/moduleloop.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmmon-only/bootstrap/monLoaderVmmon.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmmon-only/bootstrap/monLoader.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmmon-only/bootstrap/vmmblob.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmmon-only/bootstrap/bootstrap.o

/tmp/modconfig-dY8Xnm/vmmon-only/common/memtrack.o: warning: objtool: MemTrack_Cleanup()+0x4d: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmmon-only/bootstrap/monLoader.o: warning: objtool: MonLoader_Process()+0x202: indirect jump found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmmon-only/vmcore/moduleloop.o: warning: objtool: Vmx86_RunVM()+0x118: indirect jump found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmmon-only/common/task.c: In function ‘Task_Switch’:

/tmp/modconfig-dY8Xnm/vmmon-only/common/task.c:2326:7: error: invalid 'asm': invalid operand code 'V'

       __asm__ __volatile__(CALL_NOSPEC

       ^

make[2]: *** [/tmp/modconfig-dY8Xnm/vmmon-only/common/task.o] Error 1

make[2]: *** Waiting for unfinished jobs....

/tmp/modconfig-dY8Xnm/vmmon-only/linux/driver.o: warning: objtool: LinuxDriverSyncCallHook()+0x5e: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmmon-only/linux/driver.o: warning: objtool: LinuxDriver_Ioctl()+0x7c: indirect jump found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmmon-only/linux/driver.o: warning: objtool: LinuxDriver_Ioctl()+0x9c: indirect jump found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmmon-only/linux/hostif.o: warning: objtool: HostIF_SemaphoreWait()+0xd2: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmmon-only/linux/hostif.o: warning: objtool: HostIF_SemaphoreWait()+0x110: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmmon-only/linux/hostif.o: warning: objtool: HostIF_SemaphoreSignal()+0xa2: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmmon-only/linux/hostif.o: warning: objtool: HostIF_OneIPI()+0x1d: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmmon-only/linux/hostif.o: warning: objtool: HostIF_IPI()+0x8e: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmmon-only/linux/hostif.o: warning: objtool: HostIF_CallOnEachCPU()+0x15: indirect call found in RETPOLINE build

make[1]: *** [_module_/tmp/modconfig-dY8Xnm/vmmon-only] Error 2

make[1]: Leaving directory `/usr/src/kernels/5.0.1-1.el7.elrepo.x86_64'

make: *** [vmmon.ko] Error 2

make: Leaving directory `/tmp/modconfig-dY8Xnm/vmmon-only'

Using kernel build system.

make: Entering directory `/tmp/modconfig-dY8Xnm/vmnet-only'

/usr/bin/make -C /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include/.. M=$PWD SRCROOT=$PWD/. \

  MODULEBUILDDIR= modules

make[1]: Entering directory `/usr/src/kernels/5.0.1-1.el7.elrepo.x86_64'

  CC [M]  /tmp/modconfig-dY8Xnm/vmnet-only/hub.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmnet-only/driver.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmnet-only/userif.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmnet-only/netif.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmnet-only/bridge.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmnet-only/procfs.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmnet-only/smac_compat.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmnet-only/smac.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmnet-only/vnetEvent.o

  CC [M]  /tmp/modconfig-dY8Xnm/vmnet-only/vnetUserListener.o

/tmp/modconfig-dY8Xnm/vmnet-only/vnetEvent.o: warning: objtool: VNetEvent_Send()+0xef: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/vnetEvent.o: warning: objtool: VNetEvent_CreateListener()+0xc7: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/vnetUserListener.o: warning: objtool: VNetUserListenerPoll()+0x2d: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/procfs.o: warning: objtool: VNetProcShow()+0x51: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/userif.o: warning: objtool: VNetUserIfPoll()+0x2d: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/driver.o: warning: objtool: VNetFileOpRead()+0x2d: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/driver.o: warning: objtool: VNetFileOpWrite()+0x2d: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/driver.o: warning: objtool: VNetFileOpPoll()+0x31: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/driver.o: warning: objtool: VNetKrefRelease()+0x27: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/driver.o: warning: objtool: VNetConnect()+0x2f: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/driver.o: warning: objtool: VNetConnect()+0x50: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/driver.o: warning: objtool: VNetConnect()+0xb4: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/driver.o: warning: objtool: VNetConnect()+0xd3: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/driver.o: warning: objtool: VNetDisconnect()+0x56: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/driver.o: warning: objtool: VNetDisconnect()+0x6d: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/driver.o: warning: objtool: VNetSend()+0x55: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/driver.o: warning: objtool: VNetFileOpUnlockedIoctl()+0xbd: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/driver.o: warning: objtool: VNetFileOpUnlockedIoctl()+0x3cc: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/driver.o: warning: objtool: VNetFileOpUnlockedIoctl()+0x411: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/hub.o: warning: objtool: VNetHubCycleDetect()+0x56: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/hub.o: warning: objtool: VNetHubIsBridged()+0x3f: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/hub.o: warning: objtool: VNetHubPortsChanged()+0x84: indirect call found in RETPOLINE build

/tmp/modconfig-dY8Xnm/vmnet-only/bridge.o: warning: objtool: VNetCallSMACFunc()+0x53: indirect call found in RETPOLINE build

  LD [M]  /tmp/modconfig-dY8Xnm/vmnet-only/vmnet.o

  Building modules, stage 2.

  MODPOST 1 modules

  CC      /tmp/modconfig-dY8Xnm/vmnet-only/vmnet.mod.o

  LD [M]  /tmp/modconfig-dY8Xnm/vmnet-only/vmnet.ko

make[1]: Leaving directory `/usr/src/kernels/5.0.1-1.el7.elrepo.x86_64'

/usr/bin/make -C $PWD SRCROOT=$PWD/. \

  MODULEBUILDDIR= postbuild

make[1]: Entering directory `/tmp/modconfig-dY8Xnm/vmnet-only'

make[1]: `postbuild' is up to date.

make[1]: Leaving directory `/tmp/modconfig-dY8Xnm/vmnet-only'

cp -f vmnet.ko ./../vmnet.o

make: Leaving directory `/tmp/modconfig-dY8Xnm/vmnet-only'

Unable to install all modules.  See log for details.

[root@kraehe vmware-host-modules-workstation-15.0.2]#

---------------------------------------------------------------------------------------------------------------------------------------------------

After that procedure, vmnet seams to work (before the procedure it also didn't compile)

but vmmon didn't run:

2019-04-03T23:59:23.026+02:00| host-1250| I125: Log for VMware Workstation pid=1250 version=15.0.4 build=build-12990004 option=Release

2019-04-03T23:59:23.026+02:00| host-1250| I125: The process is 64-bit.

2019-04-03T23:59:23.026+02:00| host-1250| I125: Host codepage=UTF-8 encoding=UTF-8

2019-04-03T23:59:23.026+02:00| host-1250| I125: Host is Linux 5.0.1-1.el7.elrepo.x86_64 CentOS Linux release 7.6.1810 (Core)

2019-04-03T23:59:23.026+02:00| host-1250| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": Datei oder Verzeichnis nicht gefunden.

2019-04-03T23:59:23.026+02:00| host-1250| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": Datei oder Verzeichnis nicht gefunden.

2019-04-03T23:59:23.026+02:00| host-1250| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2019-04-03T23:59:23.026+02:00| host-1250| I125: DictionaryLoad: Cannot open file "/home/holger/.vmware/config": Datei oder Verzeichnis nicht gefunden.

2019-04-03T23:59:23.026+02:00| host-1250| I125: [msg.dictionary.load.openFailed] Cannot open file "/home/holger/.vmware/config": Datei oder Verzeichnis nicht gefunden.

2019-04-03T23:59:23.026+02:00| host-1250| I125: PREF Optional preferences file not found at /home/holger/.vmware/config. Using default values.

2019-04-03T23:59:23.041+02:00| host-1250| W115: Logging to /tmp/vmware-root/vmware-1250.log

2019-04-03T23:59:23.085+02:00| host-1250| I125: Obtaining info using the running kernel.

2019-04-03T23:59:23.085+02:00| host-1250| I125: Created new pathsHash.

2019-04-03T23:59:23.086+02:00| host-1250| I125: Setting header path for 5.0.1-1.el7.elrepo.x86_64 to "/lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include".

2019-04-03T23:59:23.086+02:00| host-1250| I125: Validating path "/lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include" for kernel release "5.0.1-1.el7.elrepo.x86_64".

2019-04-03T23:59:23.086+02:00| host-1250| I125: Failed to find /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include/linux/version.h

2019-04-03T23:59:23.086+02:00| host-1250| I125: /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-04-03T23:59:23.086+02:00| host-1250| I125: using /usr/local/bin/gcc for preprocess check

2019-04-03T23:59:23.095+02:00| host-1250| I125: Preprocessed UTS_RELEASE, got value "5.0.1-1.el7.elrepo.x86_64".

2019-04-03T23:59:23.095+02:00| host-1250| I125: The header path "/lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include" for the kernel "5.0.1-1.el7.elrepo.x86_64" is valid.  Whoohoo!

2019-04-03T23:59:23.255+02:00| host-1250| I125: found symbol version file /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/Module.symvers

2019-04-03T23:59:23.255+02:00| host-1250| I125: Reading symbol versions from /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/Module.symvers.

2019-04-03T23:59:23.274+02:00| host-1250| I125: Read 20013 symbol versions

2019-04-03T23:59:23.274+02:00| host-1250| I125: Reading in info for the vmmon module.

2019-04-03T23:59:23.274+02:00| host-1250| I125: Reading in info for the vmnet module.

2019-04-03T23:59:23.274+02:00| host-1250| I125: Reading in info for the vmci module.

2019-04-03T23:59:23.274+02:00| host-1250| I125: Reading in info for the vsock module.

2019-04-03T23:59:23.274+02:00| host-1250| I125: Setting vsock to depend on vmci.

2019-04-03T23:59:23.274+02:00| host-1250| I125: Invoking modinfo on "vmmon".

2019-04-03T23:59:23.278+02:00| host-1250| I125: "/sbin/modinfo" exited with status 256.

2019-04-03T23:59:23.278+02:00| host-1250| I125: Invoking modinfo on "vmnet".

2019-04-03T23:59:23.280+02:00| host-1250| I125: "/sbin/modinfo" exited with status 0.

2019-04-03T23:59:23.280+02:00| host-1250| I125: Invoking modinfo on "vmci".

2019-04-03T23:59:23.283+02:00| host-1250| I125: "/sbin/modinfo" exited with status 256.

2019-04-03T23:59:23.283+02:00| host-1250| I125: Invoking modinfo on "vsock".

2019-04-03T23:59:23.286+02:00| host-1250| I125: "/sbin/modinfo" exited with status 0.

2019-04-03T23:59:23.298+02:00| host-1250| I125: to be installed: vmmon status: 0

2019-04-03T23:59:23.311+02:00| host-1250| I125: Obtaining info using the running kernel.

2019-04-03T23:59:23.311+02:00| host-1250| I125: Setting header path for 5.0.1-1.el7.elrepo.x86_64 to "/lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include".

2019-04-03T23:59:23.311+02:00| host-1250| I125: Validating path "/lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include" for kernel release "5.0.1-1.el7.elrepo.x86_64".

2019-04-03T23:59:23.312+02:00| host-1250| I125: Failed to find /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include/linux/version.h

2019-04-03T23:59:23.312+02:00| host-1250| I125: /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-04-03T23:59:23.312+02:00| host-1250| I125: using /usr/local/bin/gcc for preprocess check

2019-04-03T23:59:23.322+02:00| host-1250| I125: Preprocessed UTS_RELEASE, got value "5.0.1-1.el7.elrepo.x86_64".

2019-04-03T23:59:23.323+02:00| host-1250| I125: The header path "/lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include" for the kernel "5.0.1-1.el7.elrepo.x86_64" is valid.  Whoohoo!

2019-04-03T23:59:23.477+02:00| host-1250| I125: found symbol version file /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/Module.symvers

2019-04-03T23:59:23.477+02:00| host-1250| I125: Reading symbol versions from /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/Module.symvers.

2019-04-03T23:59:23.495+02:00| host-1250| I125: Read 20013 symbol versions

2019-04-03T23:59:23.496+02:00| host-1250| I125: Kernel header path retrieved from FileEntry: /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include

2019-04-03T23:59:23.496+02:00| host-1250| I125: Update kernel header path to /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include

2019-04-03T23:59:23.496+02:00| host-1250| I125: Validating path "/lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include" for kernel release "5.0.1-1.el7.elrepo.x86_64".

2019-04-03T23:59:23.496+02:00| host-1250| I125: Failed to find /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include/linux/version.h

2019-04-03T23:59:23.496+02:00| host-1250| I125: /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-04-03T23:59:23.496+02:00| host-1250| I125: using /usr/local/bin/gcc for preprocess check

2019-04-03T23:59:23.507+02:00| host-1250| I125: Preprocessed UTS_RELEASE, got value "5.0.1-1.el7.elrepo.x86_64".

2019-04-03T23:59:23.507+02:00| host-1250| I125: The header path "/lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include" for the kernel "5.0.1-1.el7.elrepo.x86_64" is valid.  Whoohoo!

2019-04-03T23:59:23.509+02:00| host-1250| I125: Found compiler at "/usr/local/bin/gcc"

2019-04-03T23:59:23.513+02:00| host-1250| I125: Got gcc version "4.9.2".

2019-04-03T23:59:23.513+02:00| host-1250| I125: GCC minor version 4 does not match Kernel GCC minor version 4.  But that is ok.

2019-04-03T23:59:23.518+02:00| host-1250| I125: Got gcc version "4.9.2".

2019-04-03T23:59:23.518+02:00| host-1250| I125: GCC minor version 4 does not match Kernel GCC minor version 4.  But that is ok.

2019-04-03T23:59:23.521+02:00| host-1250| I125: Trying to find a suitable PBM set for kernel "5.0.1-1.el7.elrepo.x86_64".

2019-04-03T23:59:23.521+02:00| host-1250| I125: No matching PBM set was found for kernel "5.0.1-1.el7.elrepo.x86_64".

2019-04-03T23:59:23.521+02:00| host-1250| I125: GCC minor version 4 does not match Kernel GCC minor version 4.  But that is ok.

2019-04-03T23:59:23.521+02:00| host-1250| I125: Validating path "/lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include" for kernel release "5.0.1-1.el7.elrepo.x86_64".

2019-04-03T23:59:23.521+02:00| host-1250| I125: Failed to find /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include/linux/version.h

2019-04-03T23:59:23.521+02:00| host-1250| I125: /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-04-03T23:59:23.521+02:00| host-1250| I125: using /usr/local/bin/gcc for preprocess check

2019-04-03T23:59:23.532+02:00| host-1250| I125: Preprocessed UTS_RELEASE, got value "5.0.1-1.el7.elrepo.x86_64".

2019-04-03T23:59:23.532+02:00| host-1250| I125: The header path "/lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include" for the kernel "5.0.1-1.el7.elrepo.x86_64" is valid.  Whoohoo!

2019-04-03T23:59:23.532+02:00| host-1250| I125: GCC minor version 4 does not match Kernel GCC minor version 4.  But that is ok.

2019-04-03T23:59:23.532+02:00| host-1250| I125: Validating path "/lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include" for kernel release "5.0.1-1.el7.elrepo.x86_64".

2019-04-03T23:59:23.532+02:00| host-1250| I125: Failed to find /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include/linux/version.h

2019-04-03T23:59:23.532+02:00| host-1250| I125: /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-04-03T23:59:23.532+02:00| host-1250| I125: using /usr/local/bin/gcc for preprocess check

2019-04-03T23:59:23.542+02:00| host-1250| I125: Preprocessed UTS_RELEASE, got value "5.0.1-1.el7.elrepo.x86_64".

2019-04-03T23:59:23.542+02:00| host-1250| I125: The header path "/lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include" for the kernel "5.0.1-1.el7.elrepo.x86_64" is valid.  Whoohoo!

2019-04-03T23:59:23.542+02:00| host-1250| I125: Using temp dir "/tmp".

2019-04-03T23:59:23.545+02:00| host-1250| I125: Obtaining info using the running kernel.

2019-04-03T23:59:23.545+02:00| host-1250| I125: Setting header path for 5.0.1-1.el7.elrepo.x86_64 to "/lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include".

2019-04-03T23:59:23.545+02:00| host-1250| I125: Validating path "/lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include" for kernel release "5.0.1-1.el7.elrepo.x86_64".

2019-04-03T23:59:23.545+02:00| host-1250| I125: Failed to find /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include/linux/version.h

2019-04-03T23:59:23.545+02:00| host-1250| I125: /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2019-04-03T23:59:23.545+02:00| host-1250| I125: using /usr/local/bin/gcc for preprocess check

2019-04-03T23:59:23.555+02:00| host-1250| I125: Preprocessed UTS_RELEASE, got value "5.0.1-1.el7.elrepo.x86_64".

2019-04-03T23:59:23.555+02:00| host-1250| I125: The header path "/lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include" for the kernel "5.0.1-1.el7.elrepo.x86_64" is valid.  Whoohoo!

2019-04-03T23:59:23.713+02:00| host-1250| I125: found symbol version file /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/Module.symvers

2019-04-03T23:59:23.713+02:00| host-1250| I125: Reading symbol versions from /lib/modules/5.0.1-1.el7.elrepo.x86_64/build/Module.symvers.

2019-04-03T23:59:23.731+02:00| host-1250| I125: Read 20013 symbol versions

2019-04-03T23:59:23.731+02:00| host-1250| I125: Invoking modinfo on "vmmon".

2019-04-03T23:59:23.735+02:00| host-1250| I125: "/sbin/modinfo" exited with status 256.

2019-04-03T23:59:23.867+02:00| host-1250| I125: Setting destination path for vmmon to "/lib/modules/5.0.1-1.el7.elrepo.x86_64/misc/vmmon.ko".

2019-04-03T23:59:23.868+02:00| host-1250| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2019-04-03T23:59:23.883+02:00| host-1250| I125: Successfully extracted the vmmon source.

2019-04-03T23:59:23.883+02:00| host-1250| I125: Building module with command "/usr/bin/make -j16 -C /tmp/modconfig-ZsMK5Y/vmmon-only auto-build HEADER_DIR=/lib/modules/5.0.1-1.el7.elrepo.x86_64/build/include CC=/usr/local/bin/gcc IS_GCC_3=no"

2019-04-03T23:59:26.004+02:00| host-1250| W115: Failed to build vmmon.  Failed to execute the build command.

Hope, that somebody knows the solution.

Greetings from Germany.

Holger

Reply
0 Kudos
mkubecek
Hot Shot
Hot Shot
Jump to solution

I just tried build of workstation-15.0.4 branch (which is the same as 15.0.2) against 5.0.1-1.el7.elrepo.x86_64 CentOS kernel and it builds cleanly (on openSUSE Leap 15.0 - I didn't want to install a complete CentOS system). So your problem rather seems to be caused either by some mess with kernel devel packages or something wrong with the toolchain. In any case, "invalid 'asm': invalid operand cde 'V'" looks wrong: apart from the typo, it should read "...invalid operand for code 'V'".

Reply
0 Kudos
crorion
Contributor
Contributor
Jump to solution

5.0.7-200.fc29.x86_64

Fix above still works for this version.

Just had to recompile and install the same package again.

Sorry if this is obvious. It seems helpful to keep the discussion going, as Fedora keeps us prancing upon our fingertips with its ¨cutting-edge¨ releases.

mkubecek

Thanks again for the release.

Reply
0 Kudos
crorion
Contributor
Contributor
Jump to solution

5.0.9-200.fc29.x86_64 works as-well.

Reply
0 Kudos