VMware Communities
salinero27
Contributor
Contributor

Unable to start Virtual Machine Monitor

Hi,

When I try to run my VMWare Workstation 14.0.0 build-6661328 on my Debian GNU/Linux buster/sid 64-bit , VMware tries to compile and load several modules before run and shows an error compiling Virtual Machine monitor.

Starting VMware services:

   Virtual machine monitor                                  failed

   Virtual machine communication interface       done

   VM communication interface socket family     done

   Blocking file system                                        done

   Virtual ethernet                                               done

   VMware Authentication Daemon                    done

The log file shows the below information:

2018-04-16T09:28:03.877+02:00| vthread-1| I125: Log for VMware Workstation pid=31708 version=14.0.0 build=build-6661328 option=Release

2018-04-16T09:28:03.877+02:00| vthread-1| I125: The process is 64-bit.

2018-04-16T09:28:03.877+02:00| vthread-1| I125: Host codepage=UTF-8 encoding=UTF-8

2018-04-16T09:28:03.877+02:00| vthread-1| I125: Host is Linux 4.15.0-2-amd64 Debian GNU/Linux testing (buster)

2018-04-16T09:28:03.877+02:00| vthread-1| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No existe el fichero o el directorio.

2018-04-16T09:28:03.877+02:00| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No existe el fichero o el directorio.

2018-04-16T09:28:03.877+02:00| vthread-1| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2018-04-16T09:28:03.877+02:00| vthread-1| I125: DictionaryLoad: Cannot open file "/home/tiotocho/.vmware/config": No existe el fichero o el directorio.

2018-04-16T09:28:03.877+02:00| vthread-1| I125: [msg.dictionary.load.openFailed] Cannot open file "/home/tiotocho/.vmware/config": No existe el fichero o el directorio.

2018-04-16T09:28:03.877+02:00| vthread-1| I125: PREF Optional preferences file not found at /home/tiotocho/.vmware/config. Using default values.

2018-04-16T09:28:03.980+02:00| vthread-1| W115: Logging to /tmp/vmware-root/vmware-31708.log

2018-04-16T09:28:03.988+02:00| vthread-1| I125: Obtaining info using the running kernel.

2018-04-16T09:28:03.988+02:00| vthread-1| I125: Created new pathsHash.

2018-04-16T09:28:03.988+02:00| vthread-1| I125: Setting header path for 4.15.0-2-amd64 to "/lib/modules/4.15.0-2-amd64/build/include".

2018-04-16T09:28:03.988+02:00| vthread-1| I125: Validating path "/lib/modules/4.15.0-2-amd64/build/include" for kernel release "4.15.0-2-amd64".

2018-04-16T09:28:03.988+02:00| vthread-1| I125: Failed to find /lib/modules/4.15.0-2-amd64/build/include/linux/version.h

2018-04-16T09:28:03.988+02:00| vthread-1| I125: /lib/modules/4.15.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-04-16T09:28:03.988+02:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2018-04-16T09:28:03.993+02:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.0-2-amd64".

2018-04-16T09:28:03.993+02:00| vthread-1| I125: The header path "/lib/modules/4.15.0-2-amd64/build/include" for the kernel "4.15.0-2-amd64" is valid.  Whoohoo!

2018-04-16T09:28:04.102+02:00| vthread-1| I125: found symbol version file /lib/modules/4.15.0-2-amd64/build/Module.symvers

2018-04-16T09:28:04.102+02:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.15.0-2-amd64/build/Module.symvers.

2018-04-16T09:28:04.116+02:00| vthread-1| I125: Read 20056 symbol versions

2018-04-16T09:28:04.116+02:00| vthread-1| I125: Reading in info for the vmmon module.

2018-04-16T09:28:04.116+02:00| vthread-1| I125: Reading in info for the vmnet module.

2018-04-16T09:28:04.116+02:00| vthread-1| I125: Reading in info for the vmblock module.

2018-04-16T09:28:04.116+02:00| vthread-1| I125: Reading in info for the vmci module.

2018-04-16T09:28:04.116+02:00| vthread-1| I125: Reading in info for the vsock module.

2018-04-16T09:28:04.116+02:00| vthread-1| I125: Setting vsock to depend on vmci.

2018-04-16T09:28:04.116+02:00| vthread-1| I125: Invoking modinfo on "vmmon".

2018-04-16T09:28:04.118+02:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-04-16T09:28:04.118+02:00| vthread-1| I125: Invoking modinfo on "vmnet".

2018-04-16T09:28:04.119+02:00| vthread-1| I125: "/sbin/modinfo" exited with status 0.

2018-04-16T09:28:04.119+02:00| vthread-1| I125: Invoking modinfo on "vmblock".

2018-04-16T09:28:04.121+02:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-04-16T09:28:04.121+02:00| vthread-1| I125: Invoking modinfo on "vmci".

2018-04-16T09:28:04.122+02:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-04-16T09:28:04.122+02:00| vthread-1| I125: Invoking modinfo on "vsock".

2018-04-16T09:28:04.124+02:00| vthread-1| I125: "/sbin/modinfo" exited with status 0.

2018-04-16T09:28:04.134+02:00| vthread-1| I125: to be installed: vmmon status: 0

2018-04-16T09:28:04.140+02:00| vthread-1| I125: Obtaining info using the running kernel.

2018-04-16T09:28:04.140+02:00| vthread-1| I125: Setting header path for 4.15.0-2-amd64 to "/lib/modules/4.15.0-2-amd64/build/include".

2018-04-16T09:28:04.140+02:00| vthread-1| I125: Validating path "/lib/modules/4.15.0-2-amd64/build/include" for kernel release "4.15.0-2-amd64".

2018-04-16T09:28:04.140+02:00| vthread-1| I125: Failed to find /lib/modules/4.15.0-2-amd64/build/include/linux/version.h

2018-04-16T09:28:04.140+02:00| vthread-1| I125: /lib/modules/4.15.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-04-16T09:28:04.140+02:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2018-04-16T09:28:04.147+02:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.0-2-amd64".

2018-04-16T09:28:04.147+02:00| vthread-1| I125: The header path "/lib/modules/4.15.0-2-amd64/build/include" for the kernel "4.15.0-2-amd64" is valid.  Whoohoo!

2018-04-16T09:28:04.257+02:00| vthread-1| I125: found symbol version file /lib/modules/4.15.0-2-amd64/build/Module.symvers

2018-04-16T09:28:04.257+02:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.15.0-2-amd64/build/Module.symvers.

2018-04-16T09:28:04.270+02:00| vthread-1| I125: Read 20056 symbol versions

2018-04-16T09:28:04.270+02:00| vthread-1| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.15.0-2-amd64/build/include

2018-04-16T09:28:04.270+02:00| vthread-1| I125: Update kernel header path to /lib/modules/4.15.0-2-amd64/build/include

2018-04-16T09:28:04.270+02:00| vthread-1| I125: Validating path "/lib/modules/4.15.0-2-amd64/build/include" for kernel release "4.15.0-2-amd64".

2018-04-16T09:28:04.270+02:00| vthread-1| I125: Failed to find /lib/modules/4.15.0-2-amd64/build/include/linux/version.h

2018-04-16T09:28:04.270+02:00| vthread-1| I125: /lib/modules/4.15.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-04-16T09:28:04.270+02:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2018-04-16T09:28:04.276+02:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.0-2-amd64".

2018-04-16T09:28:04.276+02:00| vthread-1| I125: The header path "/lib/modules/4.15.0-2-amd64/build/include" for the kernel "4.15.0-2-amd64" is valid.  Whoohoo!

2018-04-16T09:28:04.277+02:00| vthread-1| I125: Found compiler at "/usr/bin/gcc"

2018-04-16T09:28:04.279+02:00| vthread-1| I125: Got gcc version "7".

2018-04-16T09:28:04.279+02:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-04-16T09:28:04.282+02:00| vthread-1| I125: Got gcc version "7".

2018-04-16T09:28:04.282+02:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-04-16T09:28:04.283+02:00| vthread-1| I125: Trying to find a suitable PBM set for kernel "4.15.0-2-amd64".

2018-04-16T09:28:04.283+02:00| vthread-1| I125: No matching PBM set was found for kernel "4.15.0-2-amd64".

2018-04-16T09:28:04.283+02:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-04-16T09:28:04.283+02:00| vthread-1| I125: Validating path "/lib/modules/4.15.0-2-amd64/build/include" for kernel release "4.15.0-2-amd64".

2018-04-16T09:28:04.283+02:00| vthread-1| I125: Failed to find /lib/modules/4.15.0-2-amd64/build/include/linux/version.h

2018-04-16T09:28:04.283+02:00| vthread-1| I125: /lib/modules/4.15.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-04-16T09:28:04.283+02:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2018-04-16T09:28:04.290+02:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.0-2-amd64".

2018-04-16T09:28:04.290+02:00| vthread-1| I125: The header path "/lib/modules/4.15.0-2-amd64/build/include" for the kernel "4.15.0-2-amd64" is valid.  Whoohoo!

2018-04-16T09:28:04.292+02:00| vthread-1| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-04-16T09:28:04.292+02:00| vthread-1| I125: Validating path "/lib/modules/4.15.0-2-amd64/build/include" for kernel release "4.15.0-2-amd64".

2018-04-16T09:28:04.292+02:00| vthread-1| I125: Failed to find /lib/modules/4.15.0-2-amd64/build/include/linux/version.h

2018-04-16T09:28:04.292+02:00| vthread-1| I125: /lib/modules/4.15.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-04-16T09:28:04.292+02:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2018-04-16T09:28:04.299+02:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.0-2-amd64".

2018-04-16T09:28:04.299+02:00| vthread-1| I125: The header path "/lib/modules/4.15.0-2-amd64/build/include" for the kernel "4.15.0-2-amd64" is valid.  Whoohoo!

2018-04-16T09:28:04.299+02:00| vthread-1| I125: Using temp dir "/tmp".

2018-04-16T09:28:04.301+02:00| vthread-1| I125: Obtaining info using the running kernel.

2018-04-16T09:28:04.301+02:00| vthread-1| I125: Setting header path for 4.15.0-2-amd64 to "/lib/modules/4.15.0-2-amd64/build/include".

2018-04-16T09:28:04.301+02:00| vthread-1| I125: Validating path "/lib/modules/4.15.0-2-amd64/build/include" for kernel release "4.15.0-2-amd64".

2018-04-16T09:28:04.301+02:00| vthread-1| I125: Failed to find /lib/modules/4.15.0-2-amd64/build/include/linux/version.h

2018-04-16T09:28:04.301+02:00| vthread-1| I125: /lib/modules/4.15.0-2-amd64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-04-16T09:28:04.301+02:00| vthread-1| I125: using /usr/bin/gcc-7 for preprocess check

2018-04-16T09:28:04.309+02:00| vthread-1| I125: Preprocessed UTS_RELEASE, got value "4.15.0-2-amd64".

2018-04-16T09:28:04.309+02:00| vthread-1| I125: The header path "/lib/modules/4.15.0-2-amd64/build/include" for the kernel "4.15.0-2-amd64" is valid.  Whoohoo!

2018-04-16T09:28:04.422+02:00| vthread-1| I125: found symbol version file /lib/modules/4.15.0-2-amd64/build/Module.symvers

2018-04-16T09:28:04.422+02:00| vthread-1| I125: Reading symbol versions from /lib/modules/4.15.0-2-amd64/build/Module.symvers.

2018-04-16T09:28:04.435+02:00| vthread-1| I125: Read 20056 symbol versions

2018-04-16T09:28:04.435+02:00| vthread-1| I125: Invoking modinfo on "vmmon".

2018-04-16T09:28:04.437+02:00| vthread-1| I125: "/sbin/modinfo" exited with status 256.

2018-04-16T09:28:05.242+02:00| vthread-1| I125: Setting destination path for vmmon to "/lib/modules/4.15.0-2-amd64/misc/vmmon.ko".

2018-04-16T09:28:05.242+02:00| vthread-1| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2018-04-16T09:28:05.254+02:00| vthread-1| I125: Successfully extracted the vmmon source.

2018-04-16T09:28:05.254+02:00| vthread-1| I125: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-0vhSlZ/vmmon-only auto-build HEADER_DIR=/lib/modules/4.15.0-2-amd64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2018-04-16T09:28:07.057+02:00| vthread-1| W115: Failed to build vmmon.  Failed to execute the build command.

Until now, VMWare worked correctly, so I don know where is the problem...

When I installed vmware at firts time, I had to patch the Vmmon service using the patch in the below URL:

Re: Not enough physical memory is available

Thanks in advance

0 Kudos
0 Replies