VMware Communities
HenryE3
Contributor
Contributor
Jump to solution

Workstation 9.0.3 modules won't compile in linux kernel 3.13.0-24

Hi,

I recently upgraded to Linux Mint 17, and have been trying to re-install Workstation 9, but keep getting the same error.

I've downloaded the latest version, 9.0.3, but it still fails to compile vmnet.ko, vmblock.ko, or vmci.ko.

Here's the latest log file:

2014-06-29T04:56:27.125-08:00| modconfig| I120: Log for VMware Workstation pid=8605 version=9.0.2 build=build-1031769 option=Release

2014-06-29T04:56:27.125-08:00| modconfig| I120: The process is 64-bit.

2014-06-29T04:56:27.125-08:00| modconfig| I120: Host codepage=UTF-8 encoding=UTF-8

2014-06-29T04:56:27.125-08:00| modconfig| I120: Host is Linux 3.13.0-24-generic Linux Mint 17 Qiana

2014-06-29T04:56:27.125-08:00| modconfig| I120: Msg_Reset:

2014-06-29T04:56:27.125-08:00| modconfig| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2014-06-29T04:56:27.125-08:00| modconfig| I120: ----------------------------------------

2014-06-29T04:56:27.125-08:00| modconfig| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2014-06-29T04:56:27.125-08:00| modconfig| I120: Msg_Reset:

2014-06-29T04:56:27.125-08:00| modconfig| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.

2014-06-29T04:56:27.125-08:00| modconfig| I120: ----------------------------------------

2014-06-29T04:56:27.125-08:00| modconfig| I120: PREF Optional preferences file not found at /root/.vmware/config. Using default values.

2014-06-29T04:56:27.125-08:00| modconfig| I120: Msg_Reset:

2014-06-29T04:56:27.125-08:00| modconfig| I120: [msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": No such file or directory.

2014-06-29T04:56:27.125-08:00| modconfig| I120: ----------------------------------------

2014-06-29T04:56:27.125-08:00| modconfig| I120: PREF Failed to load user preferences.

2014-06-29T04:56:27.125-08:00| modconfig| I120: Initialized!  Lets do this thing...

2014-06-29T04:56:27.126-08:00| modconfig| I120: Obtaining info using the running kernel.

2014-06-29T04:56:27.126-08:00| modconfig| I120: Setting header path for 3.13.0-24-generic to "/lib/modules/3.13.0-24-generic/build/include".

2014-06-29T04:56:27.126-08:00| modconfig| I120: Validating path "/lib/modules/3.13.0-24-generic/build/include" for kernel release "3.13.0-24-generic".

2014-06-29T04:56:27.126-08:00| modconfig| I120: Created new pathsHash.

2014-06-29T04:56:27.135-08:00| modconfig| I120: Preprocessed UTS_RELEASE, got value "3.13.0-24-generic".

2014-06-29T04:56:27.135-08:00| modconfig| I120: The header path "/lib/modules/3.13.0-24-generic/build/include" for the kernel "3.13.0-24-generic" is valid.  Whoohoo!

2014-06-29T04:56:27.267-08:00| modconfig| I120: Reading in info for the vmmon module.

2014-06-29T04:56:27.267-08:00| modconfig| I120: Reading in info for the vmnet module.

2014-06-29T04:56:27.267-08:00| modconfig| I120: Reading in info for the vmblock module.

2014-06-29T04:56:27.267-08:00| modconfig| I120: Reading in info for the vmci module.

2014-06-29T04:56:27.267-08:00| modconfig| I120: Reading in info for the vsock module.

2014-06-29T04:56:27.267-08:00| modconfig| I120: Setting vsock to depend on vmci.

2014-06-29T04:56:27.268-08:00| modconfig| I120: Trying to find a suitable PBM set for kernel "3.13.0-24-generic".

2014-06-29T04:56:27.268-08:00| modconfig| I120: No matching PBM set was found for kernel "3.13.0-24-generic".

2014-06-29T04:56:27.268-08:00| modconfig| I120: Found compiler at "/usr/bin/gcc"

2014-06-29T04:56:27.271-08:00| modconfig| I120: Got gcc version "4.8".

2014-06-29T04:56:27.271-08:00| modconfig| I120: The GCC version matches the kernel GCC minor version like a glove.

2014-06-29T04:56:27.271-08:00| modconfig| I120: Using temp dir "/tmp".

2014-06-29T04:56:27.485-08:00| modconfig| I120: Setting destination path for vmmon to "/lib/modules/3.13.0-24-generic/misc/vmmon.ko".

2014-06-29T04:56:27.485-08:00| modconfig| I120: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2014-06-29T04:56:27.510-08:00| modconfig| I120: Successfully extracted the vmmon source.

2014-06-29T04:56:27.510-08:00| modconfig| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-iu1wD2/vmmon-only auto-build HEADER_DIR=/lib/modules/3.13.0-24-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2014-06-29T04:56:29.008-08:00| modconfig| I120: Successfully built vmmon.  Module is currently at "/tmp/modconfig-iu1wD2/vmmon.o".

2014-06-29T04:56:29.008-08:00| modconfig| I120: Found the vmmon symvers file at "/tmp/modconfig-iu1wD2/vmmon-only/Module.symvers".

2014-06-29T04:56:29.008-08:00| modconfig| I120: Installing vmmon from /tmp/modconfig-iu1wD2/vmmon.o to /lib/modules/3.13.0-24-generic/misc/vmmon.ko.

2014-06-29T04:56:29.008-08:00| modconfig| I120: Registering file "/lib/modules/3.13.0-24-generic/misc/vmmon.ko".

2014-06-29T04:56:29.754-08:00| modconfig| I120: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

2014-06-29T04:56:29.754-08:00| modconfig| I120: Registering file "/usr/lib/vmware/symvers/vmmon-3.13.0-24-generic".

2014-06-29T04:56:29.988-08:00| modconfig| I120: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

2014-06-29T04:56:29.988-08:00| modconfig| I120: Setting destination path for vmnet to "/lib/modules/3.13.0-24-generic/misc/vmnet.ko".

2014-06-29T04:56:29.988-08:00| modconfig| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

2014-06-29T04:56:29.995-08:00| modconfig| I120: Successfully extracted the vmnet source.

2014-06-29T04:56:29.996-08:00| modconfig| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-iu1wD2/vmnet-only auto-build HEADER_DIR=/lib/modules/3.13.0-24-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2014-06-29T04:56:31.321-08:00| modconfig| W110: Failed to build vmnet.  Failed to execute the build command.

2014-06-29T04:56:31.321-08:00| modconfig| I120: Setting destination path for vmblock to "/lib/modules/3.13.0-24-generic/misc/vmblock.ko".

2014-06-29T04:56:31.321-08:00| modconfig| I120: Extracting the vmblock source from "/usr/lib/vmware/modules/source/vmblock.tar".

2014-06-29T04:56:31.325-08:00| modconfig| I120: Successfully extracted the vmblock source.

2014-06-29T04:56:31.325-08:00| modconfig| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-iu1wD2/vmblock-only auto-build HEADER_DIR=/lib/modules/3.13.0-24-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2014-06-29T04:56:32.462-08:00| modconfig| W110: Failed to build vmblock.  Failed to execute the build command.

2014-06-29T04:56:32.462-08:00| modconfig| I120: Setting destination path for vmci to "/lib/modules/3.13.0-24-generic/misc/vmci.ko".

2014-06-29T04:56:32.462-08:00| modconfig| I120: Extracting the vmci source from "/usr/lib/vmware/modules/source/vmci.tar".

2014-06-29T04:56:32.472-08:00| modconfig| I120: Successfully extracted the vmci source.

2014-06-29T04:56:32.472-08:00| modconfig| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-iu1wD2/vmci-only auto-build HEADER_DIR=/lib/modules/3.13.0-24-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2014-06-29T04:56:33.473-08:00| modconfig| W110: Failed to build vmci.  Failed to execute the build command.

2014-06-29T04:56:33.474-08:00| modconfig| I120: Setting destination path for vsock to "/lib/modules/3.13.0-24-generic/misc/vsock.ko".

2014-06-29T04:56:33.474-08:00| modconfig| I120: Extracting the vsock source from "/usr/lib/vmware/modules/source/vsock.tar".

2014-06-29T04:56:33.491-08:00| modconfig| I120: Successfully extracted the vsock source.

2014-06-29T04:56:33.491-08:00| modconfig| I120: The vmci module has already undergone compilation.

2014-06-29T04:56:33.504-08:00| modconfig| I120: We are now shutdown.  Ready to die!


Any help would be appreciated.  Thanks.

0 Kudos
1 Solution

Accepted Solutions
tigerike
Contributor
Contributor
Jump to solution

I just got the workstation 9.0.4 vmnet driver to compile on ubuntu 14.04 64bit using the patch and instructions here:

procedure below if from here (says it is a patch for workstation 10 that they ran on a 3.13 kernel but it worked fine for me.

http://ping8888.com/2013/12/13/vmware-modules-kernel-3-13/

Here’s the module patch: (Updated: Thanks DanDar3)

205a206

> #if LINUX_VERSION_CODE < KERNEL_VERSION(3, 13, 0)

206a208,210

> #else

> VNetFilterHookFn(const struct nf_hook_ops *ops,        // IN:

> #endif

255c259,263

<    transmit = (hooknum == VMW_NF_INET_POST_ROUTING);

---

>    #if LINUX_VERSION_CODE < KERNEL_VERSION(3, 13, 0)

>       transmit = (hooknum == VMW_NF_INET_POST_ROUTING);

>    #else

>       transmit = (ops->hooknum == VMW_NF_INET_POST_ROUTING);

>    #endif

Save that text as vmnet313.patch in your home dir.

Here’s the complete steps to implement

#Change directory into the vmware module source directory

cd /usr/lib/vmware/modules/source

# untar the vmnet modules

tar -xvf vmnet.tar

#run a the patch you should have just saved earlier

patch vmnet-only/filter.c < ~/vmnet313.patch

# re-tar the modules

tar -uvf vmnet.tar vmnet-only

#delete the previous working directory

rm -r vmnet-only

# run the vmware module build program. (alternatively just run the GUI app) /usr/lib/vmware/bin/vmware-modconfig --console --install-all

View solution in original post

0 Kudos
5 Replies
Jayden56
Enthusiast
Enthusiast
Jump to solution

Hi

Welcome to communities.

Did you researched on Linux forum , it might be compatibility problem.

KumarLande
Enthusiast
Enthusiast
Jump to solution

Hey Henry,

This is purely compatibility issue. Mint is not considered as a supported host OS for Workstation yet. Below is the link for the compatibility guide which talks about all the supported host OS.

VMware Compatibility Guide: Guest/Host Search

However official running Workstation on unsupported OS is not supported. Well I do see that WS 10.0.3 works on Mint 17 LTS

Cheers..

HenryE3
Contributor
Contributor
Jump to solution

Thank you, Jayden, thank you, Kumar--

I had not been aware that VMware only supported selected distributions-- And since Mint is closely derived from Ubuntu, I'd assumed...

Anyway, that answers that.

I should also mention that I did try Workstation 10, and it did install and run right up until I hit Ctrl-Alt-Enter.  Then instead of going to fullscreen, the guest display just disappeared...

My license is only good for version 9, though, so I'll let someone else bring up that bug.

Thanks again.

Disappointedly,

     ---Henry

0 Kudos
tigerike
Contributor
Contributor
Jump to solution

I just got the workstation 9.0.4 vmnet driver to compile on ubuntu 14.04 64bit using the patch and instructions here:

procedure below if from here (says it is a patch for workstation 10 that they ran on a 3.13 kernel but it worked fine for me.

http://ping8888.com/2013/12/13/vmware-modules-kernel-3-13/

Here’s the module patch: (Updated: Thanks DanDar3)

205a206

> #if LINUX_VERSION_CODE < KERNEL_VERSION(3, 13, 0)

206a208,210

> #else

> VNetFilterHookFn(const struct nf_hook_ops *ops,        // IN:

> #endif

255c259,263

<    transmit = (hooknum == VMW_NF_INET_POST_ROUTING);

---

>    #if LINUX_VERSION_CODE < KERNEL_VERSION(3, 13, 0)

>       transmit = (hooknum == VMW_NF_INET_POST_ROUTING);

>    #else

>       transmit = (ops->hooknum == VMW_NF_INET_POST_ROUTING);

>    #endif

Save that text as vmnet313.patch in your home dir.

Here’s the complete steps to implement

#Change directory into the vmware module source directory

cd /usr/lib/vmware/modules/source

# untar the vmnet modules

tar -xvf vmnet.tar

#run a the patch you should have just saved earlier

patch vmnet-only/filter.c < ~/vmnet313.patch

# re-tar the modules

tar -uvf vmnet.tar vmnet-only

#delete the previous working directory

rm -r vmnet-only

# run the vmware module build program. (alternatively just run the GUI app) /usr/lib/vmware/bin/vmware-modconfig --console --install-all

0 Kudos
HenryE3
Contributor
Contributor
Jump to solution

Thanks, tigerike.

Yeah, that worked.  Except for the bit at the end about running vmware-modcofig:  on my install vmware-modconfig-console is a seperate program (and didn't want to run, but since the gui program worked fine, I didn't chase it down).

0 Kudos