VMware unable to start services

Hi I am using Fedora 30 on my Lenovo Ideapad 310 I have trying to install VMware workstation or VMware player but the both in the same error VMware unable to start services See log file tmp/vmware-root/vmware-4868.log file detail
And the log file is here,

**2019-05-06T16:54:26.119+03:00| host-4868| I125: Log for VMware Workstation pid=4868 version=15.0.4 build=build-12990004 option=Release**
**2019-05-06T16:54:26.119+03:00| host-4868| I125: The process is 64-bit.**
**2019-05-06T16:54:26.119+03:00| host-4868| I125: Host codepage=UTF-8 encoding=UTF-8**
**2019-05-06T16:54:26.119+03:00| host-4868| I125: Host is Linux 5.0.11-300.fc30.x86_64 Fedora release 30 (Thirty)**
**2019-05-06T16:54:26.119+03:00| host-4868| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.**
**2019-05-06T16:54:26.119+03:00| host-4868| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.**
**2019-05-06T16:54:26.119+03:00| host-4868| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.**
**2019-05-06T16:54:26.119+03:00| host-4868| I125: DictionaryLoad: Cannot open file "/home/mahdi/.vmware/config": No such file or directory.**
**2019-05-06T16:54:26.119+03:00| host-4868| I125: [msg.dictionary.load.openFailed] Cannot open file "/home/mahdi/.vmware/config": No such file or directory.**
**2019-05-06T16:54:26.119+03:00| host-4868| I125: PREF Optional preferences file not found at /home/mahdi/.vmware/config. Using default values.**
**2019-05-06T16:54:26.119+03:00| host-4868| I125: DictionaryLoad: Cannot open file "/home/mahdi/.vmware/preferences": No such file or directory.**
**2019-05-06T16:54:26.119+03:00| host-4868| I125: [msg.dictionary.load.openFailed] Cannot open file "/home/mahdi/.vmware/preferences": No such file or directory.**
**2019-05-06T16:54:26.119+03:00| host-4868| I125: PREF Optional preferences file not found at /home/mahdi/.vmware/preferences. Using default values.**
**2019-05-06T16:54:26.130+03:00| host-4868| W115: Logging to /tmp/vmware-root/vmware-4868.log**
**2019-05-06T16:54:26.139+03:00| host-4868| I125: Obtaining info using the running kernel.**
**2019-05-06T16:54:26.139+03:00| host-4868| I125: Created new pathsHash.**
**2019-05-06T16:54:26.139+03:00| host-4868| I125: Setting header path for 5.0.11-300.fc30.x86_64 to "/lib/modules/5.0.11-300.fc30.x86_64/build/include".**
**2019-05-06T16:54:26.139+03:00| host-4868| I125: Validating path "/lib/modules/5.0.11-300.fc30.x86_64/build/include" for kernel release "5.0.11-300.fc30.x86_64".**
**2019-05-06T16:54:26.139+03:00| host-4868| I125: Failed to find /lib/modules/5.0.11-300.fc30.x86_64/build/include/linux/version.h**
**2019-05-06T16:54:26.139+03:00| host-4868| I125: /lib/modules/5.0.11-300.fc30.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.**
**2019-05-06T16:54:26.139+03:00| host-4868| I125: using /usr/bin/gcc for preprocess check**
**2019-05-06T16:54:26.144+03:00| host-4868| I125: Preprocessed UTS_RELEASE, got value "5.0.11-300.fc30.x86_64".**
**2019-05-06T16:54:26.144+03:00| host-4868| I125: The header path "/lib/modules/5.0.11-300.fc30.x86_64/build/include" for the kernel "5.0.11-300.fc30.x86_64" is valid.  Whoohoo!**
**2019-05-06T16:54:26.351+03:00| host-4868| I125: found symbol version file /lib/modules/5.0.11-300.fc30.x86_64/build/Module.symvers**
**2019-05-06T16:54:26.351+03:00| host-4868| I125: Reading symbol versions from /lib/modules/5.0.11-300.fc30.x86_64/build/Module.symvers.**
**2019-05-06T16:54:26.369+03:00| host-4868| I125: Read 20631 symbol versions**
**2019-05-06T16:54:26.369+03:00| host-4868| I125: Reading in info for the vmmon module.**
**2019-05-06T16:54:26.369+03:00| host-4868| I125: Reading in info for the vmnet module.**
**2019-05-06T16:54:26.369+03:00| host-4868| I125: Reading in info for the vmci module.**
**2019-05-06T16:54:26.369+03:00| host-4868| I125: Reading in info for the vsock module.**
**2019-05-06T16:54:26.369+03:00| host-4868| I125: Setting vsock to depend on vmci.**
**2019-05-06T16:54:26.369+03:00| host-4868| I125: Invoking modinfo on "vmmon".**
**2019-05-06T16:54:26.371+03:00| host-4868| I125: "/sbin/modinfo" exited with status 256.**
**2019-05-06T16:54:26.371+03:00| host-4868| I125: Invoking modinfo on "vmnet".**
**2019-05-06T16:54:26.373+03:00| host-4868| I125: "/sbin/modinfo" exited with status 256.**
**2019-05-06T16:54:26.373+03:00| host-4868| I125: Invoking modinfo on "vmci".**
**2019-05-06T16:54:26.374+03:00| host-4868| I125: "/sbin/modinfo" exited with status 256.**
**2019-05-06T16:54:26.374+03:00| host-4868| I125: Invoking modinfo on "vsock".**
**2019-05-06T16:54:26.377+03:00| host-4868| I125: "/sbin/modinfo" exited with status 0.**
**2019-05-06T16:54:26.387+03:00| host-4868| I125: to be installed: vmmon status: 0**
**2019-05-06T16:54:26.387+03:00| host-4868| I125: to be installed: vmnet status: 0**
**2019-05-06T16:54:26.398+03:00| host-4868| I125: Obtaining info using the running kernel.**
**2019-05-06T16:54:26.398+03:00| host-4868| I125: Setting header path for 5.0.11-300.fc30.x86_64 to "/lib/modules/5.0.11-300.fc30.x86_64/build/include".**
**2019-05-06T16:54:26.398+03:00| host-4868| I125: Validating path "/lib/modules/5.0.11-300.fc30.x86_64/build/include" for kernel release "5.0.11-300.fc30.x86_64".**
**2019-05-06T16:54:26.398+03:00| host-4868| I125: Failed to find /lib/modules/5.0.11-300.fc30.x86_64/build/include/linux/version.h**
**2019-05-06T16:54:26.398+03:00| host-4868| I125: /lib/modules/5.0.11-300.fc30.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.**
**2019-05-06T16:54:26.398+03:00| host-4868| I125: using /usr/bin/gcc for preprocess check**
**2019-05-06T16:54:26.403+03:00| host-4868| I125: Preprocessed UTS_RELEASE, got value "5.0.11-300.fc30.x86_64".**
**2019-05-06T16:54:26.403+03:00| host-4868| I125: The header path "/lib/modules/5.0.11-300.fc30.x86_64/build/include" for the kernel "5.0.11-300.fc30.x86_64" is valid.  Whoohoo!**
**2019-05-06T16:54:26.657+03:00| host-4868| I125: found symbol version file /lib/modules/5.0.11-300.fc30.x86_64/build/Module.symvers**
**2019-05-06T16:54:26.657+03:00| host-4868| I125: Reading symbol versions from /lib/modules/5.0.11-300.fc30.x86_64/build/Module.symvers.**
**2019-05-06T16:54:26.681+03:00| host-4868| I125: Read 20631 symbol versions**
**2019-05-06T16:54:26.681+03:00| host-4868| I125: Kernel header path retrieved from FileEntry: /lib/modules/5.0.11-300.fc30.x86_64/build/include**
**2019-05-06T16:54:26.681+03:00| host-4868| I125: Update kernel header path to /lib/modules/5.0.11-300.fc30.x86_64/build/include**
**2019-05-06T16:54:26.681+03:00| host-4868| I125: Validating path "/lib/modules/5.0.11-300.fc30.x86_64/build/include" for kernel release "5.0.11-300.fc30.x86_64".**
**2019-05-06T16:54:26.681+03:00| host-4868| I125: Failed to find /lib/modules/5.0.11-300.fc30.x86_64/build/include/linux/version.h**
**2019-05-06T16:54:26.681+03:00| host-4868| I125: /lib/modules/5.0.11-300.fc30.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.**
**2019-05-06T16:54:26.681+03:00| host-4868| I125: using /usr/bin/gcc for preprocess check**
**2019-05-06T16:54:26.692+03:00| host-4868| I125: Preprocessed UTS_RELEASE, got value "5.0.11-300.fc30.x86_64".**
**2019-05-06T16:54:26.692+03:00| host-4868| I125: The header path "/lib/modules/5.0.11-300.fc30.x86_64/build/include" for the kernel "5.0.11-300.fc30.x86_64" is valid.  Whoohoo!**
**2019-05-06T16:54:26.693+03:00| host-4868| I125: Found compiler at "/usr/bin/gcc"**
**2019-05-06T16:54:26.696+03:00| host-4868| I125: Got gcc version "9".**
**2019-05-06T16:54:26.696+03:00| host-4868| I125: The GCC version matches the kernel GCC minor version like a glove.**
**2019-05-06T16:54:26.699+03:00| host-4868| I125: Got gcc version "9".**
**2019-05-06T16:54:26.699+03:00| host-4868| I125: The GCC version matches the kernel GCC minor version like a glove.**
**2019-05-06T16:54:26.701+03:00| host-4868| I125: Trying to find a suitable PBM set for kernel "5.0.11-300.fc30.x86_64".**
**2019-05-06T16:54:26.701+03:00| host-4868| I125: No matching PBM set was found for kernel "5.0.11-300.fc30.x86_64".**
**2019-05-06T16:54:26.701+03:00| host-4868| I125: The GCC version matches the kernel GCC minor version like a glove.**
**2019-05-06T16:54:26.701+03:00| host-4868| I125: Validating path "/lib/modules/5.0.11-300.fc30.x86_64/build/include" for kernel release "5.0.11-300.fc30.x86_64".**
**2019-05-06T16:54:26.701+03:00| host-4868| I125: Failed to find /lib/modules/5.0.11-300.fc30.x86_64/build/include/linux/version.h**
**2019-05-06T16:54:26.701+03:00| host-4868| I125: /lib/modules/5.0.11-300.fc30.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.**
**2019-05-06T16:54:26.701+03:00| host-4868| I125: using /usr/bin/gcc for preprocess check**
**2019-05-06T16:54:26.707+03:00| host-4868| I125: Preprocessed UTS_RELEASE, got value "5.0.11-300.fc30.x86_64".**
**2019-05-06T16:54:26.707+03:00| host-4868| I125: The header path "/lib/modules/5.0.11-300.fc30.x86_64/build/include" for the kernel "5.0.11-300.fc30.x86_64" is valid.  Whoohoo!**
**2019-05-06T16:54:26.707+03:00| host-4868| I125: The GCC version matches the kernel GCC minor version like a glove.**
**2019-05-06T16:54:26.707+03:00| host-4868| I125: Validating path "/lib/modules/5.0.11-300.fc30.x86_64/build/include" for kernel release "5.0.11-300.fc30.x86_64".**
**2019-05-06T16:54:26.707+03:00| host-4868| I125: Failed to find /lib/modules/5.0.11-300.fc30.x86_64/build/include/linux/version.h**
**2019-05-06T16:54:26.707+03:00| host-4868| I125: /lib/modules/5.0.11-300.fc30.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.**
**2019-05-06T16:54:26.707+03:00| host-4868| I125: using /usr/bin/gcc for preprocess check**
**2019-05-06T16:54:26.713+03:00| host-4868| I125: Preprocessed UTS_RELEASE, got value "5.0.11-300.fc30.x86_64".**
**2019-05-06T16:54:26.713+03:00| host-4868| I125: The header path "/lib/modules/5.0.11-300.fc30.x86_64/build/include" for the kernel "5.0.11-300.fc30.x86_64" is valid.  Whoohoo!**
**2019-05-06T16:54:26.713+03:00| host-4868| I125: Using temp dir "/tmp".**
**2019-05-06T16:54:26.715+03:00| host-4868| I125: Obtaining info using the running kernel.**
**2019-05-06T16:54:26.716+03:00| host-4868| I125: Setting header path for 5.0.11-300.fc30.x86_64 to "/lib/modules/5.0.11-300.fc30.x86_64/build/include".**
**2019-05-06T16:54:26.716+03:00| host-4868| I125: Validating path "/lib/modules/5.0.11-300.fc30.x86_64/build/include" for kernel release "5.0.11-300.fc30.x86_64".**
**2019-05-06T16:54:26.716+03:00| host-4868| I125: Failed to find /lib/modules/5.0.11-300.fc30.x86_64/build/include/linux/version.h**
**2019-05-06T16:54:26.716+03:00| host-4868| I125: /lib/modules/5.0.11-300.fc30.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.**
**2019-05-06T16:54:26.716+03:00| host-4868| I125: using /usr/bin/gcc for preprocess check**
**2019-05-06T16:54:26.724+03:00| host-4868| I125: Preprocessed UTS_RELEASE, got value "5.0.11-300.fc30.x86_64".**
**2019-05-06T16:54:26.724+03:00| host-4868| I125: The header path "/lib/modules/5.0.11-300.fc30.x86_64/build/include" for the kernel "5.0.11-300.fc30.x86_64" is valid.  Whoohoo!**
**2019-05-06T16:54:26.949+03:00| host-4868| I125: found symbol version file /lib/modules/5.0.11-300.fc30.x86_64/build/Module.symvers**
**2019-05-06T16:54:26.949+03:00| host-4868| I125: Reading symbol versions from /lib/modules/5.0.11-300.fc30.x86_64/build/Module.symvers.**
**2019-05-06T16:54:26.965+03:00| host-4868| I125: Read 20631 symbol versions**
**2019-05-06T16:54:26.965+03:00| host-4868| I125: Invoking modinfo on "vmmon".**
**2019-05-06T16:54:26.967+03:00| host-4868| I125: "/sbin/modinfo" exited with status 256.**
**2019-05-06T16:54:26.967+03:00| host-4868| I125: Invoking modinfo on "vmnet".**
**2019-05-06T16:54:26.969+03:00| host-4868| I125: "/sbin/modinfo" exited with status 256.**
**2019-05-06T16:54:27.037+03:00| host-4868| I125: Setting destination path for vmmon to "/lib/modules/5.0.11-300.fc30.x86_64/misc/vmmon.ko".**
**2019-05-06T16:54:27.037+03:00| host-4868| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".**
**2019-05-06T16:54:27.046+03:00| host-4868| I125: Successfully extracted the vmmon source.**
**2019-05-06T16:54:27.046+03:00| host-4868| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-SEij1H/vmmon-only auto-build HEADER_DIR=/lib/modules/5.0.11-300.fc30.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"**
**2019-05-06T16:54:29.002+03:00| host-4868| W115: Failed to build vmmon.  Failed to execute the build command.**
**2019-05-06T16:54:29.004+03:00| host-4868| I125: Setting destination path for vmnet to "/lib/modules/5.0.11-300.fc30.x86_64/misc/vmnet.ko".**
**2019-05-06T16:54:29.004+03:00| host-4868| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".**
**2019-05-06T16:54:29.009+03:00| host-4868| I125: Successfully extracted the vmnet source.**
**2019-05-06T16:54:29.009+03:00| host-4868| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-SEij1H/vmnet-only auto-build HEADER_DIR=/lib/modules/5.0.11-300.fc30.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"**
**2019-05-06T16:54:30.739+03:00| host-4868| W115: Failed to build vmnet.  Failed to execute the build command.**

Hi, working with Vmware is always a pain every kernel release it has problem, I suggest to you try other Virtualization Platform:

  • gnome-boxes (installed by default)
  • qemu
  • kvm
  • libvirt
  • virtualbox.

You can find more info here -> https://docs.fedoraproject.org/en-US/quick-docs/ in Virtualization and How to begin on it…

First try to install

sudo dnf install kernel-devel kernel-headers gcc gcc-c++ make

and start again… If this doesn’t works is a configuration problem… see my comment…

COMMENT

The problem here is always the same vmnet and vmmon doesn’t start well or doesn’t start at all, find a PATCH deal with changes in vmmon.c and vmnet.c because something breaks or add some parameters to that files or modify and IF, I suggest to you follow this Step:

  1. know what is your kernel version?: uname -r.
  2. know your Vmware version or install the latest if you don’t have it, this don’t guarantee that you don’t find any issues.
  3. Try to find the PATCH for a specific KERNEL version and Vmware.
  4. You have to deal with sources (vmnet and vmmon) and apply fixed in both of them.
  5. Try to find the fix for the specific product Vmware and Kernel version, other fix that works before don’t guarantee to resolve your problem…

Regards.,

2 Likes

Thanks man it works .