Solved: Re: ubuntu 16.4 - after updating kernel, vmware wo...

LinuxG1rl · ‎02-16-2017

Hi,

I ran the Ubuntu 16.4 64 bit software updater and it apparently upgraded my kernel to 4.4.0-62-generic. I have VMware® Workstation 12 Pro 12.5.2 build-4638234 installed and after rebooting the computer I can no longer launch vmware.

When trying to launch via cmd, I get the following:

vmware

Gtk-Message: Failed to load module "atk-bridge": /usr/lib/x86_64-linux-gnu/libatspi.so.0: undefined symbol: g_type_class_adjust_private_offset

Gtk-Message: Failed to load module "unity-gtk-module": libunity-gtk-module.so: cannot open shared object file: No such file or directory

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

Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory

Gtk-Message: Failed to load module "atk-bridge": /usr/lib/x86_64-linux-gnu/libatspi.so.0: undefined symbol: g_type_class_adjust_private_offset

Gtk-Message: Failed to load module "unity-gtk-module": libunity-gtk-module.so: cannot open shared object file: No such file or directory

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

Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory

GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.

******************

When trying to launch via GUI I get the following errors in the attachments. Any ideas? Any help will be much appreciated, thank you so much in advance!!!

wila · ‎02-17-2017

Hi,

Your log file actually seems to suggest that it should be OK.

Meanwhile I now also tested it down here and for me vmware itself runs fine on that kernel using Ubuntu 16.04

If I try to run the GUI for the app that builds all the kernels I do get all those same errors that you had.

However, luckily there is a switch to run that app without a graphical user interface.

Try running:

$ sudo /usr/bin/vmware-modconfig --console --install-all

WIth a bit of luck it gets you past the problem. If not then it is possible that one of the prerequisites like a compiler or kernel headers are missing.

The above statement should either succeed or return some errors, it probably shows some warnings though, those are not a problem.

If there's errors and it still does not work please post back the output of the command above (copy & paste is fine)

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva

View solution in original post

LinuxG1rl · ‎02-16-2017

I found this but: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=21464...

a) I dont know if it is the correct solution.

b) I dont understand the instructions - what do they mean by "Replace MOK with the name of the file you want for the key." - how do I know which name I should give the key?

BTW - I don't even know if my Ubuntu runs with UEFI, I just know that I got all these errors I described in my first post both on cmd and gui, but I don't their origin so I don't know if that vm kb is the answer.

Any help is highly appreciated, desperate here 😞

BTW: doing apt-get install libcanberra-gtk-module did not work and adding this "export LD_LIBRARY_PATH=/usr/lib/vmware/lib/libglibmm-2.4.so.1/:$LD_LIBRARY_PATH" to various files /usr/bin files also did not work.

Thanks!

Kitty

wila · ‎02-16-2017

Hi,

All the gtk errors/warnings are a red herring. They do not prevent you from using VMware Workstation.

The real problem is that you are missing one or more kernel modules (like vmmon) because they cannot be compiled on your new kernel.

Can you attach /tmp/vmware-root/vmware-4182.log to a reply here?

Also note that if you need this to work -right now- then reboot your host and select the previous kernel in your boot menu.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva

LinuxG1rl · ‎02-16-2017

Hi wila, you are always here to help the community - AMAZING! So many thanks!! Here is the log. I dont need it to work right now, but just out of curiosity, how do I choose a previous kernel on boot, dont remember how to do that. And another question, the fact that vmon is missing is not UEFI's fault as the vmware KB suggested (and which I dont know if I use)?

cat /tmp/vmware-root/vmware-4182.log

2017-02-16T23:17:41.350+02:00| vthread-4| I125: Log for VMware Workstation pid=4182 version=12.5.2 build=build-4638234 option=Release

2017-02-16T23:17:41.350+02:00| vthread-4| I125: The process is 64-bit.

2017-02-16T23:17:41.350+02:00| vthread-4| I125: Host codepage=UTF-8 encoding=UTF-8

2017-02-16T23:17:41.350+02:00| vthread-4| I125: Host is Linux 4.4.0-62-generic Ubuntu 16.04.2 LTS

2017-02-16T23:17:41.254+02:00| vthread-4| I125: DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2017-02-16T23:17:41.254+02:00| vthread-4| I125: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2017-02-16T23:17:41.281+02:00| vthread-4| I125: DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.

2017-02-16T23:17:41.281+02:00| vthread-4| I125: PREF Optional preferences file not found at /root/.vmware/config. Using default values.

2017-02-16T23:17:41.400+02:00| vthread-4| W115: Logging to /tmp/vmware-root/vmware-4182.log

2017-02-16T23:17:41.438+02:00| vthread-4| I125: Obtaining info using the running kernel.

2017-02-16T23:17:41.438+02:00| vthread-4| I125: Created new pathsHash.

2017-02-16T23:17:41.438+02:00| vthread-4| I125: Setting header path for 4.4.0-62-generic to "/lib/modules/4.4.0-62-generic/build/include".

2017-02-16T23:17:41.438+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:17:41.438+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:17:41.438+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:17:41.438+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:17:41.443+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:17:41.443+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid. Whoohoo!

2017-02-16T23:17:41.564+02:00| vthread-4| I125: found symbol version file /lib/modules/4.4.0-62-generic/build/Module.symvers

2017-02-16T23:17:41.564+02:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.0-62-generic/build/Module.symvers.

2017-02-16T23:17:41.580+02:00| vthread-4| I125: Read 18828 symbol versions

2017-02-16T23:17:41.580+02:00| vthread-4| I125: Reading in info for the vmmon module.

2017-02-16T23:17:41.580+02:00| vthread-4| I125: Reading in info for the vmnet module.

2017-02-16T23:17:41.580+02:00| vthread-4| I125: Reading in info for the vmblock module.

2017-02-16T23:17:41.580+02:00| vthread-4| I125: Reading in info for the vmci module.

2017-02-16T23:17:41.580+02:00| vthread-4| I125: Reading in info for the vsock module.

2017-02-16T23:17:41.580+02:00| vthread-4| I125: Setting vsock to depend on vmci.

2017-02-16T23:17:41.580+02:00| vthread-4| I125: Invoking modinfo on "vmmon".

2017-02-16T23:17:41.581+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-16T23:17:41.581+02:00| vthread-4| I125: Invoking modinfo on "vmnet".

2017-02-16T23:17:41.582+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-16T23:17:41.582+02:00| vthread-4| I125: Invoking modinfo on "vmblock".

2017-02-16T23:17:41.583+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-16T23:17:41.583+02:00| vthread-4| I125: Invoking modinfo on "vmci".

2017-02-16T23:17:41.584+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-16T23:17:41.584+02:00| vthread-4| I125: Invoking modinfo on "vsock".

2017-02-16T23:17:41.585+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

2017-02-16T23:17:41.595+02:00| vthread-4| I125: to be installed: vmmon status: 0

2017-02-16T23:17:41.595+02:00| vthread-4| I125: to be installed: vmnet status: 0

2017-02-16T23:17:41.650+02:00| vthread-4| I125: Obtaining info using the running kernel.

2017-02-16T23:17:41.650+02:00| vthread-4| I125: Setting header path for 4.4.0-62-generic to "/lib/modules/4.4.0-62-generic/build/include".

2017-02-16T23:17:41.650+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:17:41.650+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:17:41.650+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:17:41.650+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:17:41.656+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:17:41.656+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid. Whoohoo!

2017-02-16T23:17:41.776+02:00| vthread-4| I125: found symbol version file /lib/modules/4.4.0-62-generic/build/Module.symvers

2017-02-16T23:17:41.776+02:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.0-62-generic/build/Module.symvers.

2017-02-16T23:17:41.791+02:00| vthread-4| I125: Read 18828 symbol versions

2017-02-16T23:17:41.791+02:00| vthread-4| I125: Kernel header path retrieved from FileEntry: /lib/modules/4.4.0-62-generic/build/include

2017-02-16T23:17:41.791+02:00| vthread-4| I125: Update kernel header path to /lib/modules/4.4.0-62-generic/build/include

2017-02-16T23:17:41.791+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:17:41.791+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:17:41.791+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:17:41.791+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:17:41.796+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:17:41.797+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid. Whoohoo!

2017-02-16T23:17:41.797+02:00| vthread-4| I125: Found compiler at "/usr/bin/gcc"

2017-02-16T23:17:41.799+02:00| vthread-4| I125: Got gcc version "5.4.0".

2017-02-16T23:17:41.799+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-02-16T23:17:41.799+02:00| vthread-4| I125: Using user supplied compiler "/usr/bin/gcc".

2017-02-16T23:17:41.801+02:00| vthread-4| I125: Got gcc version "5.4.0".

2017-02-16T23:17:41.801+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-02-16T23:17:41.802+02:00| vthread-4| I125: Trying to find a suitable PBM set for kernel "4.4.0-62-generic".

2017-02-16T23:17:41.802+02:00| vthread-4| I125: No matching PBM set was found for kernel "4.4.0-62-generic".

2017-02-16T23:17:41.803+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-02-16T23:17:41.803+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:17:41.803+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:17:41.803+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:17:41.803+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:17:41.808+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:17:41.808+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid. Whoohoo!

2017-02-16T23:17:41.809+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-02-16T23:17:41.809+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:17:41.809+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:17:41.809+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:17:41.809+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:17:41.814+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:17:41.814+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid. Whoohoo!

2017-02-16T23:17:41.814+02:00| vthread-4| I125: Using temp dir "/tmp".

2017-02-16T23:17:41.815+02:00| vthread-4| I125: Obtaining info using the running kernel.

2017-02-16T23:17:41.815+02:00| vthread-4| I125: Setting header path for 4.4.0-62-generic to "/lib/modules/4.4.0-62-generic/build/include".

2017-02-16T23:17:41.815+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:17:41.815+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:17:41.815+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:17:41.815+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:17:41.820+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:17:41.820+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid. Whoohoo!

2017-02-16T23:17:41.933+02:00| vthread-4| I125: found symbol version file /lib/modules/4.4.0-62-generic/build/Module.symvers

2017-02-16T23:17:41.933+02:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.0-62-generic/build/Module.symvers.

2017-02-16T23:17:41.948+02:00| vthread-4| I125: Read 18828 symbol versions

2017-02-16T23:17:41.948+02:00| vthread-4| I125: Invoking modinfo on "vmmon".

2017-02-16T23:17:41.950+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-16T23:17:41.950+02:00| vthread-4| I125: Invoking modinfo on "vmnet".

2017-02-16T23:17:41.951+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 256.

2017-02-16T23:17:42.231+02:00| vthread-4| I125: Setting destination path for vmmon to "/lib/modules/4.4.0-62-generic/misc/vmmon.ko".

2017-02-16T23:17:42.231+02:00| vthread-4| I125: Extracting the vmmon source from "/usr/lib/vmware/modules/source/vmmon.tar".

2017-02-16T23:17:42.236+02:00| vthread-4| I125: Successfully extracted the vmmon source.

2017-02-16T23:17:42.237+02:00| vthread-4| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-wWZAu8/vmmon-only auto-build HEADER_DIR=/lib/modules/4.4.0-62-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2017-02-16T23:17:43.873+02:00| vthread-4| I125: Successfully built vmmon. Module is currently at "/tmp/modconfig-wWZAu8/vmmon.o".

2017-02-16T23:17:43.873+02:00| vthread-4| I125: Found the vmmon symvers file at "/tmp/modconfig-wWZAu8/vmmon-only/Module.symvers".

2017-02-16T23:17:43.873+02:00| vthread-4| I125: Installing vmmon from /tmp/modconfig-wWZAu8/vmmon.o to /lib/modules/4.4.0-62-generic/misc/vmmon.ko.

2017-02-16T23:17:43.873+02:00| vthread-4| I125: Registering file "/lib/modules/4.4.0-62-generic/misc/vmmon.ko".

2017-02-16T23:17:45.750+02:00| vthread-4| I125: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

2017-02-16T23:17:45.750+02:00| vthread-4| I125: Registering file "/usr/lib/vmware/symvers/vmmon-4.4.0-62-generic".

2017-02-16T23:17:46.390+02:00| vthread-4| I125: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

2017-02-16T23:17:46.392+02:00| vthread-4| I125: Setting destination path for vmnet to "/lib/modules/4.4.0-62-generic/misc/vmnet.ko".

2017-02-16T23:17:46.392+02:00| vthread-4| I125: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".

2017-02-16T23:17:46.398+02:00| vthread-4| I125: Successfully extracted the vmnet source.

2017-02-16T23:17:46.398+02:00| vthread-4| I125: Building module with command "/usr/bin/make -j4 -C /tmp/modconfig-wWZAu8/vmnet-only auto-build HEADER_DIR=/lib/modules/4.4.0-62-generic/build/include CC=/usr/bin/gcc IS_GCC_3=no"

2017-02-16T23:17:48.387+02:00| vthread-4| I125: Successfully built vmnet. Module is currently at "/tmp/modconfig-wWZAu8/vmnet.o".

2017-02-16T23:17:48.387+02:00| vthread-4| I125: Found the vmnet symvers file at "/tmp/modconfig-wWZAu8/vmnet-only/Module.symvers".

2017-02-16T23:17:48.387+02:00| vthread-4| I125: Installing vmnet from /tmp/modconfig-wWZAu8/vmnet.o to /lib/modules/4.4.0-62-generic/misc/vmnet.ko.

2017-02-16T23:17:48.388+02:00| vthread-4| I125: Registering file "/lib/modules/4.4.0-62-generic/misc/vmnet.ko".

2017-02-16T23:17:48.972+02:00| vthread-4| I125: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

2017-02-16T23:17:48.972+02:00| vthread-4| I125: Registering file "/usr/lib/vmware/symvers/vmnet-4.4.0-62-generic".

2017-02-16T23:17:49.600+02:00| vthread-4| I125: "/usr/lib/vmware-installer/2.1.0/vmware-installer" exited with status 0.

2017-02-16T23:19:12.202+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-02-16T23:19:12.202+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:19:12.202+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:19:12.203+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:19:12.203+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:19:12.210+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:19:12.210+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid. Whoohoo!

2017-02-16T23:19:12.211+02:00| vthread-4| I125: Using temp dir "/tmp".

2017-02-16T23:19:12.211+02:00| vthread-4| I125: Obtaining info using the running kernel.

2017-02-16T23:19:12.211+02:00| vthread-4| I125: Setting header path for 4.4.0-62-generic to "/lib/modules/4.4.0-62-generic/build/include".

2017-02-16T23:19:12.211+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:19:12.211+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:19:12.211+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:19:12.211+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:19:12.219+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:19:12.219+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid. Whoohoo!

2017-02-16T23:19:12.379+02:00| vthread-4| I125: found symbol version file /lib/modules/4.4.0-62-generic/build/Module.symvers

2017-02-16T23:19:12.379+02:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.0-62-generic/build/Module.symvers.

2017-02-16T23:19:12.398+02:00| vthread-4| I125: Read 18828 symbol versions

2017-02-16T23:19:12.398+02:00| vthread-4| I125: Invoking modinfo on "vmmon".

2017-02-16T23:19:12.400+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

2017-02-16T23:19:12.400+02:00| vthread-4| I125: Invoking modinfo on "vmnet".

2017-02-16T23:19:12.402+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

2017-02-16T23:19:20.731+02:00| vthread-4| I125: The GCC version matches the kernel GCC minor version like a glove.

2017-02-16T23:19:20.732+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:19:20.732+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:19:20.732+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:19:20.732+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:19:20.740+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:19:20.740+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid. Whoohoo!

2017-02-16T23:19:20.740+02:00| vthread-4| I125: Using temp dir "/tmp".

2017-02-16T23:19:20.741+02:00| vthread-4| I125: Obtaining info using the running kernel.

2017-02-16T23:19:20.741+02:00| vthread-4| I125: Setting header path for 4.4.0-62-generic to "/lib/modules/4.4.0-62-generic/build/include".

2017-02-16T23:19:20.741+02:00| vthread-4| I125: Validating path "/lib/modules/4.4.0-62-generic/build/include" for kernel release "4.4.0-62-generic".

2017-02-16T23:19:20.741+02:00| vthread-4| I125: Failed to find /lib/modules/4.4.0-62-generic/build/include/linux/version.h

2017-02-16T23:19:20.741+02:00| vthread-4| I125: /lib/modules/4.4.0-62-generic/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.

2017-02-16T23:19:20.741+02:00| vthread-4| I125: using /usr/bin/gcc for preprocess check

2017-02-16T23:19:20.750+02:00| vthread-4| I125: Preprocessed UTS_RELEASE, got value "4.4.0-62-generic".

2017-02-16T23:19:20.750+02:00| vthread-4| I125: The header path "/lib/modules/4.4.0-62-generic/build/include" for the kernel "4.4.0-62-generic" is valid. Whoohoo!

2017-02-16T23:19:20.914+02:00| vthread-4| I125: found symbol version file /lib/modules/4.4.0-62-generic/build/Module.symvers

2017-02-16T23:19:20.914+02:00| vthread-4| I125: Reading symbol versions from /lib/modules/4.4.0-62-generic/build/Module.symvers.

2017-02-16T23:19:20.934+02:00| vthread-4| I125: Read 18828 symbol versions

2017-02-16T23:19:20.934+02:00| vthread-4| I125: Invoking modinfo on "vmmon".

2017-02-16T23:19:20.936+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

2017-02-16T23:19:20.936+02:00| vthread-4| I125: Invoking modinfo on "vmnet".

2017-02-16T23:19:20.938+02:00| vthread-4| I125: "/sbin/modinfo" exited with status 0.

wila · ‎02-16-2017

Hi,

Sorry no time atm for looking over the log file (next time please attach using the link at the bottom right instead of copy&paste the contents)

For booting an older kernel you use the grub menu, if there's no delay set then you either have to be very fast with the escape key or.. hold down shift while booting.

See also:

http://askubuntu.com/questions/82140/how-can-i-boot-with-an-older-kernel-version#82145

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva

LinuxG1rl · ‎02-16-2017

Hi wil, that's OK, I will wait until you have time to take a look at it, I don't want to be using older kernels, I want it to work with the current one, let me know when you have time and if you need more info from me.

And if anyone else has time to take a look or ideas it is more than welcome!

Many thanks!!!

bonnie201110141 · ‎02-16-2017

Did you install open-vm-tools in you Ubuntu 16.04 host? Or are you running Ubuntu 16.04 as a VM?

wila · ‎02-17-2017

Hi,

Your log file actually seems to suggest that it should be OK.

Meanwhile I now also tested it down here and for me vmware itself runs fine on that kernel using Ubuntu 16.04

If I try to run the GUI for the app that builds all the kernels I do get all those same errors that you had.

However, luckily there is a switch to run that app without a graphical user interface.

Try running:

$ sudo /usr/bin/vmware-modconfig --console --install-all

WIth a bit of luck it gets you past the problem. If not then it is possible that one of the prerequisites like a compiler or kernel headers are missing.

The above statement should either succeed or return some errors, it probably shows some warnings though, those are not a problem.

If there's errors and it still does not work please post back the output of the command above (copy & paste is fine)

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva

LinuxG1rl · ‎02-18-2017

bonnie201110141‌ - My Ubuntu is the main OS, not running it as a VM.

wila - I did as you told me and I still got the same errors when trying to run the VM via GUI ir Terminal, see attached. Many many thanks for the help!! I attached another file as well with some additional results of commands that I read could help find the problem, called For_Wila

LinuxG1rl · ‎02-18-2017

wila‌ - problem solved thanks to you. I saw in the output of the command you gave me that the problem was that the vmnet process was running and could not be killed. I killed it, ran your command again and now it is working. I am SO grateful, you can't even imagine.

If you don't mind me asking and taking your time - I want to learn a bit more about what happened and how you got to this conclusion. Because every time I upgrade the linux kernel, I get the same problem with vmware, sometimes a bit different, but usually around the same lines - and the solution each time is something different. Most of the times you are the one who solved it for me. How can I learn how to solve this problem if every time the solution is different?

I ask because I know it will happen again next time I upgrade the kernel (I like my OS to be always as up to date as possible, so I don't want to NOT upgrade the kernel only because it will break something in the VM).

Are there any guidelines that you can teach me or point me to a place where I can read more about these issues? No promises I wont need your help next time again, but at least I will feel less dumb 😄

I also am not sure what you meant by "However, luckily there is a switch to run that app without a graphical user interface." - what do you mean by run the app without a graphical interface? After I ran the command you gave me, I clicked on the VM icon and it opened everything in GUI, I didnt need to open the vm by runnin

/usr/bin/vmware-modconfig --console --install-all

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-j5AMbH/vmmon-only'

Using kernel build system.

/usr/bin/make -C /lib/modules/4.4.0-62-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

MODULEBUILDDIR= modules

make[1]: Entering directory '/usr/src/linux-headers-4.4.0-62-generic'

CC [M] /tmp/modconfig-j5AMbH/vmmon-only/linux/driver.o

CC [M] /tmp/modconfig-j5AMbH/vmmon-only/linux/hostif.o

CC [M] /tmp/modconfig-j5AMbH/vmmon-only/linux/driverLog.o

CC [M] /tmp/modconfig-j5AMbH/vmmon-only/common/memtrack.o

CC [M] /tmp/modconfig-j5AMbH/vmmon-only/common/apic.o

CC [M] /tmp/modconfig-j5AMbH/vmmon-only/common/hashFunc.o

CC [M] /tmp/modconfig-j5AMbH/vmmon-only/common/vmx86.o

CC [M] /tmp/modconfig-j5AMbH/vmmon-only/common/cpuid.o

/tmp/modconfig-j5AMbH/vmmon-only/linux/driver.c:1283:1: warning: always_inline function might not be inlinable [-Wattributes]

LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min

^

CC [M] /tmp/modconfig-j5AMbH/vmmon-only/common/task.o

/tmp/modconfig-j5AMbH/vmmon-only/linux/driver.c: In function ‘LinuxDriver_Ioctl’:

/tmp/modconfig-j5AMbH/vmmon-only/linux/driver.c:1981:1: warning: the frame size of 1168 bytes is larger than 1024 bytes [-Wframe-larger-than=]

}

^

CC [M] /tmp/modconfig-j5AMbH/vmmon-only/common/comport.o

CC [M] /tmp/modconfig-j5AMbH/vmmon-only/common/phystrack.o

CC [M] /tmp/modconfig-j5AMbH/vmmon-only/vmcore/moduleloop.o

LD [M] /tmp/modconfig-j5AMbH/vmmon-only/vmmon.o

Building modules, stage 2.

MODPOST 1 modules

CC /tmp/modconfig-j5AMbH/vmmon-only/vmmon.mod.o

LD [M] /tmp/modconfig-j5AMbH/vmmon-only/vmmon.ko

make[1]: Leaving directory '/usr/src/linux-headers-4.4.0-62-generic'

/usr/bin/make -C $PWD SRCROOT=$PWD/. \

MODULEBUILDDIR= postbuild

make[1]: Entering directory '/tmp/modconfig-j5AMbH/vmmon-only'

make[1]: 'postbuild' is up to date.

make[1]: Leaving directory '/tmp/modconfig-j5AMbH/vmmon-only'

cp -f vmmon.ko ./../vmmon.o

make: Leaving directory '/tmp/modconfig-j5AMbH/vmmon-only'

make: Entering directory '/tmp/modconfig-j5AMbH/vmnet-only'

Using kernel build system.

/usr/bin/make -C /lib/modules/4.4.0-62-generic/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \

MODULEBUILDDIR= modules

make[1]: Entering directory '/usr/src/linux-headers-4.4.0-62-generic'

CC [M] /tmp/modconfig-j5AMbH/vmnet-only/driver.o

CC [M] /tmp/modconfig-j5AMbH/vmnet-only/hub.o

CC [M] /tmp/modconfig-j5AMbH/vmnet-only/userif.o

CC [M] /tmp/modconfig-j5AMbH/vmnet-only/netif.o

In file included from include/linux/pci.h:35:0,

from /tmp/modconfig-j5AMbH/vmnet-only/compat_netdevice.h:27,

from /tmp/modconfig-j5AMbH/vmnet-only/netif.c:43:

include/linux/pci_ids.h:2252:0: warning: "PCI_VENDOR_ID_VMWARE" redefined

#define PCI_VENDOR_ID_VMWARE 0x15ad

^

In file included from /tmp/modconfig-j5AMbH/vmnet-only/net.h:38:0,

from /tmp/modconfig-j5AMbH/vmnet-only/vnetInt.h:26,

from /tmp/modconfig-j5AMbH/vmnet-only/netif.c:42:

/tmp/modconfig-j5AMbH/vmnet-only/vm_device_version.h:56:0: note: this is the location of the previous definition

#define PCI_VENDOR_ID_VMWARE 0x15AD

^

CC [M] /tmp/modconfig-j5AMbH/vmnet-only/bridge.o

CC [M] /tmp/modconfig-j5AMbH/vmnet-only/procfs.o

CC [M] /tmp/modconfig-j5AMbH/vmnet-only/smac_compat.o

CC [M] /tmp/modconfig-j5AMbH/vmnet-only/smac.o

CC [M] /tmp/modconfig-j5AMbH/vmnet-only/vnetEvent.o

In file included from /tmp/modconfig-j5AMbH/vmnet-only/net.h:38:0,

from /tmp/modconfig-j5AMbH/vmnet-only/vnetInt.h:26,

from /tmp/modconfig-j5AMbH/vmnet-only/bridge.c:52:

/tmp/modconfig-j5AMbH/vmnet-only/vm_device_version.h:56:0: warning: "PCI_VENDOR_ID_VMWARE" redefined

#define PCI_VENDOR_ID_VMWARE 0x15AD

^

In file included from include/linux/pci.h:35:0,

from /tmp/modconfig-j5AMbH/vmnet-only/compat_netdevice.h:27,

from /tmp/modconfig-j5AMbH/vmnet-only/bridge.c:51:

include/linux/pci_ids.h:2252:0: note: this is the location of the previous definition

#define PCI_VENDOR_ID_VMWARE 0x15ad

^

CC [M] /tmp/modconfig-j5AMbH/vmnet-only/vnetUserListener.o

LD [M] /tmp/modconfig-j5AMbH/vmnet-only/vmnet.o

Building modules, stage 2.

MODPOST 1 modules

CC /tmp/modconfig-j5AMbH/vmnet-only/vmnet.mod.o

LD [M] /tmp/modconfig-j5AMbH/vmnet-only/vmnet.ko

make[1]: Leaving directory '/usr/src/linux-headers-4.4.0-62-generic'

/usr/bin/make -C $PWD SRCROOT=$PWD/. \

MODULEBUILDDIR= postbuild

make[1]: Entering directory '/tmp/modconfig-j5AMbH/vmnet-only'

make[1]: 'postbuild' is up to date.

make[1]: Leaving directory '/tmp/modconfig-j5AMbH/vmnet-only'

cp -f vmnet.ko ./../vmnet.o

make: Leaving directory '/tmp/modconfig-j5AMbH/vmnet-only'

Starting VMware services:

Virtual machine monitor done

Virtual machine communication interface done

VM communication interface socket family done

Blocking file system done

Virtual ethernet done

VMware Authentication Daemon done

Shared Memory Available done

wila · ‎02-19-2017

Hi,

Glad to be of any help.

The vmware-modconfig command has a pretty graphical user interface unless you use the "--console" option. But as the graphical user interface hides all the technical details and threw a bunch of errors/warnings itself it wasn't that helpful.

As for the "how can I learn" question.

Well I'm afraid there's no simple answer. In my case I just spent -probably too much- time at these forums, so I do pick up things left and right on what to do in case of problem X.

Besides that I've been a Linux user since about 1996 or so, even while not always that active, you do bump into problems and learn bit by bit on how-to solve things.

So lots of what I learned is because of hands on experience of problems, but also because of just trying things like "so... how do I build my kernel?" and just because I read of what problems other people bump into (and hopefully also how they managed to fix that).

Besides all of that I'm a software developer in my day to day life and I target most platforms (windows/macOS/linux) so that helps too. Troubleshooting customer issues is an important skill set there.

Bumping into issues and asking around if anybody knows a solution is part of that too.

No need to feel dumb, we've all been there and in a way it is just another learning opportunity.

But, really the kernel update should have "just worked" for you. It did for me when I ran the update here.

I'm unclear as to why the update process wasn't able to unload your vmnet kernel module. If you do bump into issues next time, don't worry, we're happy to help out.

It's why these forums exist.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva

LinuxG1rl · ‎02-19-2017

What can I say after such a kind answer wila? The world is better because of people like you! Many thanks!!!

wila · ‎02-19-2017

You're most welcome.

One thing that might not be clear from the above... there's plenty of things I don't know and I learn here from others pretty much on a daily bases.

Besides that, helping others is a learning opportunity for me as well, if I don't know the answer I try and see if I can find out what a possible solution is.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva

LinuxG1rl · ‎02-22-2017

Hi Wil,

It was very clear and you most definitely chose the right path to learn and I will learn this lesson from you.

The only disadvantage I have is that I am not a coder, so it is a big "less" in IT world.

There is also the issue of time - having a full day job and a family, not always easy to find the much needed and wanted time to spend on these amazing forums - it is definitely a passion of mine and I hope to be able to find the time.

All the best and many thanks again!!

LinuxG1rl · ‎03-11-2017

Hi Wila,

Unbelievable, but it happened again. Ubuntu upgraded to a new kernel and again when trying to run vmware via the GUI I got the same error as I posted in the beginning of this thread.

I used your solution, I ran sudo /usr/bin/vmware-modconfig --console --install-all and it solved the problem like before and I thank you for that again!

But I am still very curios - why the vmware GUI doesn't manage to do that? Is there a way to dig in and find out, just for curiosity's sake?

Cheers and super thanks!

wila · ‎03-12-2017

Hi,

It's a bug.

As I mentioned earlier on I also saw the same issue and that was on a completely fresh installed Ubuntu machine.

While it might be possible to find out more details on what is going wrong, for me personally I have to draw the line by finding a workaround.

Otherwise I would probably never get back to work or back to the open source projects I tend to donate some of my time to as well.

This one is for VMware itself I'm afraid.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva

LinuxG1rl · ‎03-14-2017

Wil, kind and quick to answer as usual. You are absolutely right, don't waste your time on it, I was just curios and this is really for vmware to take care of.

All the best of luck in all your projects!

fracarfzx · ‎03-16-2017

Hello LinuxG1rl, I also use workstation with ubuntu 16.04 and I have a problem with memory management.

I verified that it is caused by the kernel 4.x version.

The problem is this: when I start a VM, all the configured memory for that VM is immediately allocated to the host. Host memory usage is not growing gradually. This problem with a kernel version 3.x does not occur.

The same thing happens to you too?

Thank you very much if you will help me!

LinuxG1rl · ‎03-16-2017

Hi there,

No, this doesn't happen to me at all, but sounds like a very curios and interesting problem to solve.

I will do some research and if I find anything that could be of use to you I will post it here.

Good luck!

fracarfzx · ‎03-16-2017

Thank you for your reply!

I'm so desperate!

In this link

VMware Workstation Pro 12 - Host Memory Allocation

You can find my previous posts.

You can read it for more info if you want.

Thank you again for your time and attention!

All

ubuntu 16.4 - after updating kernel, vmware workstation-pro 12 does not launch anymore