VMware Communities
JustinType
Contributor
Contributor

Can't run VMWare Player due to Kernel headers

I'm on Kubuntu 22.04 with a kernel version of 5.19.0-32-generic (verified with the command ```uname -a```)

I have downloaded VMWare Player 17.0.2 and installed it without problems but when I try to run it I got this error :

I have already try to add synlinks with :

cd /lib/modules/$(uname -r)/build/include/linux
sudo ln -s ../generated/utsrelease.h
sudo ln -s ../generated/autoconf.h
sudo ln -s ../generated/uapi/linux/version.h

and put the path with ```/usr/src/linux-headers-5.19.0-32-generic/include``` but it doesn't work and I got this message :

I have already verified that I got the last kernel headers with :

sudo apt-get install build-essential
sudo apt-get install linux-headers-$(uname -r)

Finally I tried this command : ```sudo vmware-modconfig --console --install-all``` and got this error :

[AppLoader] GLib does not have GSettings support.

(process:15928): GLib-CRITICAL **: 22:33:39.910: g_file_test: assertion 'filename != NULL' failed
Failed to setup build environment.

 

Do you have any ideas of how to solve this problem and run VMWare (if possible without recompiling old kernel modules), thanks.

 

Reply
0 Kudos
8 Replies
Matth_
Contributor
Contributor

I had the same issue with VMware Workstation 16. Now the same issue with the latest Workstation 17 !!! I'm using Fedora.

The only fix I had for Workstation 16 was to recompile vmware tools, every time there was a kernel update --'

When are you going to fix this VMware ?
I paid for a product that is supposed to work with linux and not even an a whole new version can't fix that ! You're a shame I really hope this get fixed quickly. 

THIS ISSUE HAS BEEN GOING FOR YEARS ! SERIOUSLY WHAT ARE YOU DOING ?

Reply
0 Kudos
RDPetruska
Leadership
Leadership

If you paid for Player, either you needed a Commercial license, or you got ripped off.

Fedora is NOT one of the Supported host OS's.  If you want formal Support, stick with one of the Supported host OS's.

Otherwise - search the forum, ask for help... Currently, user mkubeck has been keeping a patchset up to date for Linux host issues.

Reply
0 Kudos
Matth_
Contributor
Contributor

I did not paid for player... I paid for Workstation Pro version. I obviously got ripped off.

Although the issue here is with Workstation 17 trial 

Fedora IS on the supported list of host OS. https://kb.vmware.com/s/article/80807

Hopefully I'm aware of mkubeck fix (thanks to him btw) but the problem should have been fixed years ago from VMware themselves ! 

EDIT : Ok, soooooooooo... this solution
 worked for me, I'm just waiting to see if I have to this process every time I have an update, but we'll see

I was really hoping VMware would fix this with Workstation 17 but I guess I will just keep my money :upside_down_face:

TDLR : if you get this kernel header prompt try this before re-running Workstation At least it worked for me...

sudo dnf install perl gcc make kernel-headers kernel-devel -y

 

Reply
0 Kudos
Technogeezer
Immortal
Immortal

It would also help if both of the following happened:

VMware was a bit coded a bit more liberally to accommodate accepting differences in kernel headers and toolchains required to compile their modules, Right now it appears that their kernel modules work for the supported versions and the versions that were released at the time the product went to GA. If a distribution changes something in their kernel due to an update, VMware doesn't seem to want to go back and revisit that. Instead, users are forced to use mkubeck's solution which is unfortunate for a commercially supported product.

and

Linux distributions would become a bit more stable in their kernel headers and toolchains used to compile modules. It's difficult to hit a moving target and some Linux distros play fast and loose with making changes that impact things down the pipe. 

- Paul (Technogeezer)
Editor of the Unofficial Fusion Companion Guides
RDPetruska
Leadership
Leadership


@Matth_ wrote:

I did not paid for player... I paid for Workstation Pro version. I obviously got ripped off.

Although the issue here is with Workstation 17 trial 

Fedora IS on the supported list of host OS. https://kb.vmware.com/s/article/80807

 


Didn't mean to be snarky - but you did post your reply to a thread in the Workstation *Player* forum, titled "Can't run VMware *Player* due to Kernel headers".  So I had to assume you were also using Player.

And, sorry - I see that Workstation 17 is Supported on Fedora 34, 35 and 36.  In the past, Fedora was always considered bleeding edge and was never on the Supported hosts list.  I've updated my knowledge.

JustinType
Contributor
Contributor

Sorry but as I said in my post I've already tried :

 

sudo apt-get install build-essential
sudo apt-get install linux-headers-`uname -r`

 

Also I've tested this from your solution :

 

sudo apt-get -y install linux-headers-server build-essential

 

But the packet 'linux-headers-server' doesn't seem to be found by my packet manager.

I have also tried :

sudo dnf install perl gcc make kernel-headers kernel-devel -y

 and got this error :

 

/usr/lib/python3/dist-packages/dnf/const.py:22: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives
import distutils.sysconfig
/usr/lib/python3/dist-packages/dnf/const.py:22: DeprecationWarning: The distutils.sysconfig module is deprecated, use sysconfig instead
import distutils.sysconfig

 

Finally, you mentioned mkubecek, I found this repo: https://github.com/mkubecek/vmware-host-modules

Can you explain to me how to use his solution for VMWare Player 17.0.X please ?

(Sorry I'm a complete beginner in C and Linux Kernel)

Matth_
Contributor
Contributor


@RDPetruska wrote:

@Matth_ wrote:

I did not paid for player... I paid for Workstation Pro version. I obviously got ripped off.

Although the issue here is with Workstation 17 trial 

Fedora IS on the supported list of host OS. https://kb.vmware.com/s/article/80807

 


Didn't mean to be snarky - but you did post your reply to a thread in the Workstation *Player* forum, titled "Can't run VMware *Player* due to Kernel headers".  So I had to assume you were also using Player.

And, sorry - I see that Workstation 17 is Supported on Fedora 34, 35 and 36.  In the past, Fedora was always considered bleeding edge and was never on the Supported hosts list.  I've updated my knowledge.


YUP we're on Workstation Player section, I'm blind, my bad sorry sorry ^^ 

Anyway I really hope VMware staff can find a convenient solution that work out of the box...

Reply
0 Kudos
Matth_
Contributor
Contributor



@JustinType wrote:

[...]

Finally, you mentioned mkubecek, I found this repo: https://github.com/mkubecek/vmware-host-modules

Can you explain to me how to use his solution for VMWare Player 17.0.X please ?

(Sorry I'm a complete beginner in C and Linux Kernel)



Hello, THIS SOLUTION worked for my in the past for Workstation Pro 16, the thing is you have to recompile after each system update, at least in my case.

I hope this work for you https://communities.vmware.com/t5/VMware-Workstation-Pro/Compiling-vmmon-module-fails-on-linux-kerne...

Reply
0 Kudos