VMware Communities
Pavlinux
Enthusiast
Enthusiast

[PATCH]: Linux 4.14 & VMware® Workstation 14 Pro

Found keygen. Smiley Happy  Patch in attach!

vmware.png

0 Kudos
10 Replies
mfelker
Expert
Expert

I understand I think.    I've gotten Workstation 14 to work under Windows (Windows Server 2016 host) but not under Linux - specifically Debian Sid which is on kernel 4.12 which I suppose must be completely supported.   You cannot get support from VMware unless I plunk down 150 bucks for an upgrade from 12.5.7 (which works beautifully under Linux).

Since this is complaint about VMware, Inc.   I probably should refrain from uploading screenshots but I'm pissed enough that if I need to I post them again.   See attached jpgs.

0 Kudos
calc76
Enthusiast
Enthusiast

What does the following show:

vmware-modconfig --console --install-all

0 Kudos
mfelker
Expert
Expert

I may try it again but the thing is it should work out of the box on kernel 4.12.   Debian is not some esoteric OS but I might look at support.   Basically I have 30 days to play with it on Windows but I can't see $150 for a prettier GUI.

0 Kudos
calc76
Enthusiast
Enthusiast

The error you are getting sounds like you are trying to use the vmware modules for an older release with the new version. Doing what I mentioned above should force it to rebuild all the modules.

0 Kudos
backtoback
Contributor
Contributor

HI i have the same problem

OS: kali linux

with Vmware-workstation 14.0.0-6661328

and kernel 4.14.0

but i can't run the vmware it's show me this error

1.png

2.png

also after run /etc/init.d/vmware restart

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

Starting VMware services:

   Virtual machine monitor                                            failed

   Virtual machine communication interface                             done

   VM communication interface socket family                            done

   Blocking file system                                                done

   Virtual ethernet                                                   failed

   VMware Authentication Daemon                                        done

and this is also the result of  vmware-modconfig --console --install-all

[AppLoader] GLib does not have GSettings support.

gcc-7.2: error trying to exec 'cc1': execvp: No such file or directory

(process:6538): GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed

Failed to setup build environment.

Please help i tried many ways to solve this problem but can't run

also change hostif.c file to the new one from github

Thanks

regards

0 Kudos
backtoback
Contributor
Contributor

any help please ??

0 Kudos
rakotomandimby
Enthusiast
Enthusiast

You need to install the "linux-headers"

0 Kudos
Matthias_Hehnen
VMware Employee
VMware Employee

Hi Pavlinux

The recent patch you've developed to get VMware Workstation 14 running on kernel 4.14 does not work for me:

I am using

     25396          vmware_workstation_14-linux_4.14.patch

458534208      VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle

On Fedora with

$ uname -a

Linux localhost.localdomain 4.14.3-300.fc27.x86_64 #1 SMP Thu Nov 30 15:33:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

And I am getting:

$ patch VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle vmware_workstation_14-linux_4.14.patch

patching file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle

Hunk #1 FAILED at 1459.

Hunk #2 FAILED at 1467.

Hunk #3 FAILED at 1722.

Hunk #4 FAILED at 2476.

Hunk #5 FAILED at 2490.

5 out of 5 hunks FAILED -- saving rejects to file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle.rej

patching file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle

Hunk #1 FAILED at 41.

Hunk #2 FAILED at 1198.

Hunk #3 FAILED at 1273.

Hunk #4 FAILED at 1834.

Hunk #5 FAILED at 2051.

Hunk #6 FAILED at 2070.

6 out of 6 hunks FAILED -- saving rejects to file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle.rej

patching file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle

Hunk #1 FAILED at 756.

Hunk #2 FAILED at 764.

2 out of 2 hunks FAILED -- saving rejects to file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle.rej

patching file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle

Hunk #1 FAILED at 53.

Hunk #2 FAILED at 70.

2 out of 2 hunks FAILED -- saving rejects to file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle.rej

patching file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle

Hunk #1 FAILED at 25.

1 out of 1 hunk FAILED -- saving rejects to file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle.rej

patching file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle

Hunk #1 FAILED at 25.

Hunk #2 FAILED at 75.

2 out of 2 hunks FAILED -- saving rejects to file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle.rej

patching file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle

Hunk #1 FAILED at 24.

Hunk #2 FAILED at 111.

2 out of 2 hunks FAILED -- saving rejects to file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle.rej

patching file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle

Hunk #1 FAILED at 977.

1 out of 1 hunk FAILED -- saving rejects to file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle.rej

patching file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle

Hunk #1 FAILED at 1516.

1 out of 1 hunk FAILED -- saving rejects to file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle.rej

patching file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle

Hunk #1 FAILED at 19.

Hunk #2 FAILED at 53.

Hunk #3 FAILED at 70.

3 out of 3 hunks FAILED -- saving rejects to file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle.rej

patching file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle

Hunk #1 FAILED at 114.

Hunk #2 FAILED at 213.

Hunk #3 FAILED at 233.

Hunk #4 FAILED at 314.

Hunk #5 FAILED at 670.

Hunk #6 FAILED at 2882.

Hunk #7 FAILED at 3825.

Hunk #8 FAILED at 4260.

Hunk #9 FAILED at 4352.

Hunk #10 FAILED at 4590.

Hunk #11 FAILED at 4712.

Hunk #12 FAILED at 4759.

Hunk #13 FAILED at 4771.

Hunk #14 FAILED at 4809.

Hunk #15 FAILED at 4850.

Hunk #16 FAILED at 4955.

Hunk #17 FAILED at 5488.

17 out of 17 hunks FAILED -- saving rejects to file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle.rej

patching file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle

Hunk #1 FAILED at 516.

Hunk #2 FAILED at 1193.

2 out of 2 hunks FAILED -- saving rejects to file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle.rej

patching file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle

Hunk #1 FAILED at 164.

Hunk #2 FAILED at 228.

Hunk #3 FAILED at 283.

Hunk #4 FAILED at 566.

Hunk #5 FAILED at 755.

Hunk #6 FAILED at 771.

6 out of 6 hunks FAILED -- saving rejects to file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle.rej

patching file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle

Hunk #1 FAILED at 755.

Hunk #2 FAILED at 765.

2 out of 2 hunks FAILED -- saving rejects to file VMware-Workstation-Full-14.0.0-6661328.x86_64.bundle.rej

Any idea what goes wrong here?

PS:

Right now I use Workstation 14 on Kernel 4.13 - which works...

0 Kudos
jawiweb
Contributor
Contributor

Why is it so hard for vmware to have a correct installation after updating a linux kernel.

Workstation 14.1.1 does not work on kernel 4.14  ( 4.14.18-300.fc27.x86_64 )  -->  Ready to die??

Patching or changing vmware modules does not fix this issue.

2018-02-13T11:54:45.709+01:00| modconfig| I125: Log for VMware Workstation pid=4367 version=14.1.1 build=build-7528167 option=Release

2018-02-13T11:54:45.709+01:00| modconfig| I125: The process is 64-bit.

2018-02-13T11:54:45.709+01:00| modconfig| I125: Host codepage=UTF-8 encoding=UTF-8

2018-02-13T11:54:45.709+01:00| modconfig| I125: Host is Linux 4.14.18-300.fc27.x86_64 Fedora release 27 (Twenty Seven)

2018-02-13T11:54:45.706+01:00| modconfig| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2018-02-13T11:54:45.706+01:00| modconfig| I125: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2018-02-13T11:54:45.706+01:00| modconfig| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2018-02-13T11:54:45.708+01:00| modconfig| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.

2018-02-13T11:54:45.708+01:00| modconfig| I125: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.

2018-02-13T11:54:45.708+01:00| modconfig| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values.

2018-02-13T11:54:45.710+01:00| modconfig| I125: Initialized!  Lets do this thing...

2018-02-13T11:54:45.710+01:00| modconfig| I125: Obtaining info using the running kernel.

2018-02-13T11:54:45.710+01:00| modconfig| I125: Created new pathsHash.

2018-02-13T11:54:45.710+01:00| modconfig| I125: Setting header path for 4.14.18-300.fc27.x86_64 to "/lib/modules/4.14.18-300.fc27.x86_64/build/include".

2018-02-13T11:54:45.710+01:00| modconfig| I125: Validating path "/lib/modules/4.14.18-300.fc27.x86_64/build/include" for kernel release "4.14.18-300.fc27.x86_64".

2018-02-13T11:54:45.710+01:00| modconfig| I125: Failed to find /lib/modules/4.14.18-300.fc27.x86_64/build/include/linux/version.h

2018-02-13T11:54:45.710+01:00| modconfig| I125: /lib/modules/4.14.18-300.fc27.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2018-02-13T11:54:45.710+01:00| modconfig| I125: using /usr/bin/gcc for preprocess check

2018-02-13T11:54:45.714+01:00| modconfig| I125: Preprocessed UTS_RELEASE, got value "4.14.18-300.fc27.x86_64".

2018-02-13T11:54:45.714+01:00| modconfig| I125: The header path "/lib/modules/4.14.18-300.fc27.x86_64/build/include" for the kernel "4.14.18-300.fc27.x86_64" is valid.  Whoohoo!

2018-02-13T11:54:45.811+01:00| modconfig| I125: found symbol version file /lib/modules/4.14.18-300.fc27.x86_64/build/Module.symvers

2018-02-13T11:54:45.811+01:00| modconfig| I125: Reading symbol versions from /lib/modules/4.14.18-300.fc27.x86_64/build/Module.symvers.

2018-02-13T11:54:45.823+01:00| modconfig| I125: Read 19135 symbol versions

2018-02-13T11:54:45.823+01:00| modconfig| I125: Reading in info for the vmmon module.

2018-02-13T11:54:45.823+01:00| modconfig| I125: Reading in info for the vmnet module.

2018-02-13T11:54:45.823+01:00| modconfig| I125: Reading in info for the vmblock module.

2018-02-13T11:54:45.823+01:00| modconfig| I125: Reading in info for the vmci module.

2018-02-13T11:54:45.823+01:00| modconfig| I125: Reading in info for the vsock module.

2018-02-13T11:54:45.823+01:00| modconfig| I125: Setting vsock to depend on vmci.

2018-02-13T11:54:45.830+01:00| modconfig| I125: Trying to find a suitable PBM set for kernel "4.14.18-300.fc27.x86_64".

2018-02-13T11:54:45.830+01:00| modconfig| I125: No matching PBM set was found for kernel "4.14.18-300.fc27.x86_64".

2018-02-13T11:54:45.830+01:00| modconfig| I125: Found compiler at "/usr/bin/gcc"

2018-02-13T11:54:45.831+01:00| modconfig| I125: Got gcc version "7".

2018-02-13T11:54:45.831+01:00| modconfig| I125: The GCC version matches the kernel GCC minor version like a glove.

2018-02-13T11:54:45.831+01:00| modconfig| I125: Using temp dir "/tmp".

2018-02-13T11:54:45.857+01:00| modconfig| I125: Setting destination path for vmmon to "/lib/modules/4.14.18-300.fc27.x86_64/misc/vmmon.ko".

2018-02-13T11:54:45.857+01:00| modconfig| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2018-02-13T11:54:45.860+01:00| modconfig| I125: Successfully extracted the vmmon source.

2018-02-13T11:54:45.860+01:00| modconfig| I125: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-3NYDIe/vmmon-only auto-build HEADER_DIR=/lib/modules/4.14.18-300.fc27.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2018-02-13T11:54:46.597+01:00| modconfig| W115: Failed to build vmmon.  Failed to execute the build command.

2018-02-13T11:54:46.597+01:00| modconfig| I125: Setting destination path for vmnet to "/lib/modules/4.14.18-300.fc27.x86_64/misc/vmnet.ko".

2018-02-13T11:54:46.597+01:00| modconfig| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

2018-02-13T11:54:46.600+01:00| modconfig| I125: Successfully extracted the vmnet source.

2018-02-13T11:54:46.600+01:00| modconfig| I125: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-3NYDIe/vmnet-only auto-build HEADER_DIR=/lib/modules/4.14.18-300.fc27.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2018-02-13T11:54:47.329+01:00| modconfig| W115: Failed to build vmnet.  Failed to execute the build command.

2018-02-13T11:54:47.332+01:00| modconfig| I125: We are now shutdown.  Ready to die!

Practice what you preach
0 Kudos