VMWare 12 Workstation running problem

Questions about virtualization software
Forum rules
Before you post please read how to get help
Post Reply
NoX2SR
Level 1
Level 1
Posts: 3
Joined: Thu Feb 16, 2017 12:05 pm

VMWare 12 Workstation running problem

Post by NoX2SR » Thu Feb 16, 2017 12:34 pm

Hello folks :)

I'm new on this forum, but not so new like Mint user.
As you can see from subject, I have a problem with running VMWare workstation. I tried everything that I found on the internet and this forum is my last hope.

Let's start frst with all what I have and what I've done.
Linux Mint 18.1 x64; Kernel 4.4.0-53; VMWare workstation 12.0.0

I installed workstation, but I cant run it. I had more problems. First was with header. I fixed it with reinstalling. Now, when I run:

Code: Select all

sudo /etc/init.d/vmware status
I have this output:

Code: Select all

Module vmmon not loaded
Module vmnet loaded
When I run vmware, here is what I have in terminal:

Code: Select all

(vmware-modconfig:21568): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-modconfig:21568): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-modconfig:21568): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-modconfig:21568): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-modconfig:21568): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",

(vmware-modconfig:21568): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
Stopping VMware services:
   VMware Authentication Daemon                                        done
   VM communication interface socket family                            done
   Virtual machine communication interface                             done
   Virtual machine monitor                                             done
   Blocking file system                                                done
make: Entering directory '/tmp/modconfig-J1eGfe/vmmon-only'
Using kernel build system.
/usr/bin/make -C /lib/modules/4.4.0-53-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
  MODULEBUILDDIR= modules
make[1]: Entering directory '/usr/src/linux-headers-4.4.0-53-generic'
  CC [M]  /tmp/modconfig-J1eGfe/vmmon-only/linux/driver.o
  CC [M]  /tmp/modconfig-J1eGfe/vmmon-only/linux/hostif.o
/tmp/modconfig-J1eGfe/vmmon-only/linux/driver.c: In function ‘cleanup_module’:
/tmp/modconfig-J1eGfe/vmmon-only/linux/driver.c:390:8: error: void value not ignored as it ought to be
    if (misc_deregister(&linuxState.misc)) {
        ^
At top level:
/tmp/modconfig-J1eGfe/vmmon-only/linux/driver.c:1285:1: warning: always_inline function might not be inlinable [-Wattributes]
 LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
 ^
scripts/Makefile.build:258: recipe for target '/tmp/modconfig-J1eGfe/vmmon-only/linux/driver.o' failed
make[2]: *** [/tmp/modconfig-J1eGfe/vmmon-only/linux/driver.o] Error 1
make[2]: *** Waiting for unfinished jobs....
/tmp/modconfig-J1eGfe/vmmon-only/linux/hostif.c: In function ‘HostIFGetUserPages’:
/tmp/modconfig-J1eGfe/vmmon-only/linux/hostif.c:1165:13: error: implicit declaration of function ‘get_user_pages_remote’ [-Werror=implicit-function-declaration]
    retval = get_user_pages_remote(current, current->mm, (unsigned long)uvAddr,
             ^
cc1: some warnings being treated as errors
scripts/Makefile.build:258: recipe for target '/tmp/modconfig-J1eGfe/vmmon-only/linux/hostif.o' failed
make[2]: *** [/tmp/modconfig-J1eGfe/vmmon-only/linux/hostif.o] Error 1
Makefile:1418: recipe for target '_module_/tmp/modconfig-J1eGfe/vmmon-only' failed
make[1]: *** [_module_/tmp/modconfig-J1eGfe/vmmon-only] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.4.0-53-generic'
Makefile:120: recipe for target 'vmmon.ko' failed
make: *** [vmmon.ko] Error 2
make: Leaving directory '/tmp/modconfig-J1eGfe/vmmon-only'
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
As you can see, I have problem with murrine, but I have an interface started and it says that was unable to start services and it point at log file. I allready installed murine in x32 and x64 version. I found that solution on internet, but I still have that error. Here is what I can find in log file:

Code: Select all

2017-02-16T17:18:19.737+01:00| vthread-4| I125: Log for VMware Workstation pid=21568 version=12.0.0 build=build-2985596 option=Release
2017-02-16T17:18:19.737+01:00| vthread-4| I125: The process is 64-bit.
2017-02-16T17:18:19.737+01:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8
2017-02-16T17:18:19.737+01:00| vthread-4| I125: Host is Linux 4.4.0-53-generic Linux Mint 18.1 Serena
2017-02-16T17:18:19.737+01:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2017-02-16T17:18:19.737+01:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2017-02-16T17:18:19.737+01:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.
2017-02-16T17:18:19.737+01:00| vthread-4| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values.
2017-02-16T17:18:19.737+01:00| vthread-4| I125: PREF Unable to check permissions for preferences file.
2017-02-16T17:18:19.737+01:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/preferences": No such file or directory.
2017-02-16T17:18:19.737+01:00| vthread-4| I125: PREF Failed to load user preferences.
2017-02-16T17:18:19.791+01:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-21568.log
2017-02-16T17:18:19.801+01:00| vthread-4| I125: Obtaining info using the running kernel.
2017-02-16T17:18:19.801+01:00| vthread-4| I125: Created new pathsHash.
2017-02-16T17:18:19.801+01:00| vthread-4| I125: Setting header path for 4.4.0-53-generic to "/lib/modules/4.4.0-53-generic/build/include".
2017-02-16T17:18:19.801+01:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-53-generic/build/include" for kernel release "4.4.0-53-generic".
2017-02-16T17:18:19.801+01:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2017-02-16T17:18:19.808+01:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-53-generic".
2017-02-16T17:18:19.808+01:00| vthread-4| I125: The header path "/lib/modules/4.4.0-53-generic/build/include" for the kernel "4.4.0-53-generic" is valid.  Whoohoo!
2017-02-16T17:18:20.018+01:00| vthread-4| I125: found symbol version file /lib/modules/4.4.0-53-generic/build/Module.symvers
2017-02-16T17:18:20.018+01:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.0-53-generic/build/Module.symvers.
2017-02-16T17:18:20.045+01:00| vthread-4| I125: Read 18819 symbol versions
2017-02-16T17:18:20.045+01:00| vthread-4| I125: Reading in info for the vmmon module.
2017-02-16T17:18:20.045+01:00| vthread-4| I125: Reading in info for the vmnet module.
2017-02-16T17:18:20.045+01:00| vthread-4| I125: Reading in info for the vmblock module.
2017-02-16T17:18:20.045+01:00| vthread-4| I125: Reading in info for the vmci module.
2017-02-16T17:18:20.045+01:00| vthread-4| I125: Reading in info for the vsock module.
2017-02-16T17:18:20.045+01:00| vthread-4| I125: Setting vsock to depend on vmci.
2017-02-16T17:18:20.045+01:00| vthread-4| I125: Invoking modinfo on "vmmon".
2017-02-16T17:18:20.048+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2017-02-16T17:18:20.048+01:00| vthread-4| I125: Invoking modinfo on "vmnet".
2017-02-16T17:18:20.049+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
2017-02-16T17:18:20.049+01:00| vthread-4| I125: Invoking modinfo on "vmblock".
2017-02-16T17:18:20.051+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2017-02-16T17:18:20.051+01:00| vthread-4| I125: Invoking modinfo on "vmci".
2017-02-16T17:18:20.055+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2017-02-16T17:18:20.055+01:00| vthread-4| I125: Invoking modinfo on "vsock".
2017-02-16T17:18:20.057+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.
2017-02-16T17:18:20.072+01:00| vthread-4| I125: to be installed: vmmon status: 0
2017-02-16T17:18:20.101+01:00| vthread-4| I125: Obtaining info using the running kernel.
2017-02-16T17:18:20.102+01:00| vthread-4| I125: Setting header path for 4.4.0-53-generic to "/lib/modules/4.4.0-53-generic/build/include".
2017-02-16T17:18:20.102+01:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-53-generic/build/include" for kernel release "4.4.0-53-generic".
2017-02-16T17:18:20.102+01:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2017-02-16T17:18:20.109+01:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-53-generic".
2017-02-16T17:18:20.109+01:00| vthread-4| I125: The header path "/lib/modules/4.4.0-53-generic/build/include" for the kernel "4.4.0-53-generic" is valid.  Whoohoo!
2017-02-16T17:18:20.293+01:00| vthread-4| I125: found symbol version file /lib/modules/4.4.0-53-generic/build/Module.symvers
2017-02-16T17:18:20.293+01:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.0-53-generic/build/Module.symvers.
2017-02-16T17:18:20.312+01:00| vthread-4| I125: Read 18819 symbol versions
2017-02-16T17:18:20.313+01:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.4.0-53-generic/build/include
2017-02-16T17:18:20.313+01:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2017-02-16T17:18:20.319+01:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-53-generic".
2017-02-16T17:18:20.319+01:00| vthread-4| I125: The header path "/lib/modules/4.4.0-53-generic/build/include" for the kernel "4.4.0-53-generic" is valid.  Whoohoo!
2017-02-16T17:18:20.320+01:00| vthread-4| I125: Found compiler at "/usr/bin/gcc"
2017-02-16T17:18:20.322+01:00| vthread-4| I125: Got gcc version "5.4.0".
2017-02-16T17:18:20.322+01:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2017-02-16T17:18:20.322+01:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc".
2017-02-16T17:18:20.324+01:00| vthread-4| I125: Got gcc version "5.4.0".
2017-02-16T17:18:20.324+01:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2017-02-16T17:18:20.326+01:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "4.4.0-53-generic".
2017-02-16T17:18:20.326+01:00| vthread-4| I125: No matching PBM set was found for kernel "4.4.0-53-generic".
2017-02-16T17:18:20.326+01:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2017-02-16T17:18:20.326+01:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-53-generic/build/include" for kernel release "4.4.0-53-generic".
2017-02-16T17:18:20.326+01:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2017-02-16T17:18:20.332+01:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-53-generic".
2017-02-16T17:18:20.332+01:00| vthread-4| I125: The header path "/lib/modules/4.4.0-53-generic/build/include" for the kernel "4.4.0-53-generic" is valid.  Whoohoo!
2017-02-16T17:18:20.333+01:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.
2017-02-16T17:18:20.333+01:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-53-generic/build/include" for kernel release "4.4.0-53-generic".
2017-02-16T17:18:20.333+01:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2017-02-16T17:18:20.340+01:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-53-generic".
2017-02-16T17:18:20.340+01:00| vthread-4| I125: The header path "/lib/modules/4.4.0-53-generic/build/include" for the kernel "4.4.0-53-generic" is valid.  Whoohoo!
2017-02-16T17:18:20.340+01:00| vthread-4| I125: Using temp dir "/tmp".
2017-02-16T17:18:20.341+01:00| vthread-4| I125: Obtaining info using the running kernel.
2017-02-16T17:18:20.341+01:00| vthread-4| I125: Setting header path for 4.4.0-53-generic to "/lib/modules/4.4.0-53-generic/build/include".
2017-02-16T17:18:20.341+01:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-53-generic/build/include" for kernel release "4.4.0-53-generic".
2017-02-16T17:18:20.341+01:00| vthread-4| I125: using /usr/bin/gcc for preprocess check
2017-02-16T17:18:20.349+01:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-53-generic".
2017-02-16T17:18:20.349+01:00| vthread-4| I125: The header path "/lib/modules/4.4.0-53-generic/build/include" for the kernel "4.4.0-53-generic" is valid.  Whoohoo!
2017-02-16T17:18:20.539+01:00| vthread-4| I125: found symbol version file /lib/modules/4.4.0-53-generic/build/Module.symvers
2017-02-16T17:18:20.539+01:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.0-53-generic/build/Module.symvers.
2017-02-16T17:18:20.563+01:00| vthread-4| I125: Read 18819 symbol versions
2017-02-16T17:18:20.563+01:00| vthread-4| I125: Invoking modinfo on "vmmon".
2017-02-16T17:18:20.565+01:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.
2017-02-16T17:18:21.201+01:00| vthread-4| I125: Setting destination path for vmmon to "/lib/modules/4.4.0-53-generic/misc/vmmon.ko".
2017-02-16T17:18:21.201+01:00| vthread-4| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".
2017-02-16T17:18:21.219+01:00| vthread-4| I125: Successfully extracted the vmmon source.
2017-02-16T17:18:21.219+01:00| vthread-4| I125: Building module with command "/usr/bin/make -j2 -C /tmp/modconfig-J1eGfe/vmmon-only auto-build HEADER_DIR=/lib/modules/4.4.0-53-g$
2017-02-16T17:18:22.806+01:00| vthread-4| W115: Failed to build vmmon.  Failed to execute the build command.
As you can see, problem is vmmon. I found some solutions on web with changing the names of some functions inside files, but no success. If you guys need more information, let me know.
I hope we will come out with some solution here :)

Reason why I want this program on my computer is because I was running Linux on the windows host for a long time. I had some hardware problems and when I installed Linux directly on my hard, all my problems was solved :) Next thing that I have to do is installing OSX on the vmware. It was possible on windows cause I found some patches. I hope I'll find that patch for Linux cause I need to have all 3 OS-s.

Thanks for reading this long post and thanks for help :)

grumpy_geek
Level 2
Level 2
Posts: 80
Joined: Tue Jan 03, 2017 3:50 am
Contact:

Re: VMWare 12 Workstation running problem

Post by grumpy_geek » Sat Feb 18, 2017 4:02 am

NoX2SR wrote:Linux Mint 18.1 x64; Kernel 4.4.0-53; VMWare workstation 12.0.0
Workstation 12.1 ff. should compile cleanly on kernel 4.4.x (- source; cf. VMware forums).

NoX2SR
Level 1
Level 1
Posts: 3
Joined: Thu Feb 16, 2017 12:05 pm

Re: VMWare 12 Workstation running problem

Post by NoX2SR » Sat Feb 18, 2017 1:30 pm

Workstation 12.1 ff. should compile cleanly on kernel 4.4.x (- source; cf. VMware forums).
Yeah. I downloaded 12.5 and it works fine. I can't believe I didn't try that. OSX Works better on Linux host than on Windows host. Thanks.

grumpy_geek
Level 2
Level 2
Posts: 80
Joined: Tue Jan 03, 2017 3:50 am
Contact:

Re: VMWare 12 Workstation running problem

Post by grumpy_geek » Sun Feb 19, 2017 5:24 am

NoX2SR wrote:OSX Works better on Linux host than on Windows host.
The last time I virtualized an entire office network, VMware's consulting developer explicitly told me to opt for Unix / Linux as server / host system. Guess why... (Back then, I installed Debian "undiluted"; not even a graphical interface, silly me.)

NoX2SR
Level 1
Level 1
Posts: 3
Joined: Thu Feb 16, 2017 12:05 pm

Re: VMWare 12 Workstation running problem

Post by NoX2SR » Sun Feb 19, 2017 8:24 am

Lol. Shouldn't say that it works fine. Now it started killing my processor. I have intel E8500 clocked at 4.0. Is that normal to go "in red" with that processor? I didn't have that problem with windows host.
Edit:
swap memory problem. I disabled using the swap until ram is full and now it works perfect.
Btw, Mint and OSX together take 1.7 GB of ram. I can't believe :D

Post Reply

Return to “Virtualization”