VMware 16.2.3 not working on Ubuntu 22.04 LTS

[mw73]

After up grading from Ubuntu 20.04 LTS to 22.04; I tried to start VMware Workstation Pro and I got the message "Unable to install all modules" and it referred me to an error log file which I have attached to this message. Any ideas how to get around this or do I need to go back to the previous version of Linux?

Attachment(s)

vmware-4915.log   63 KB 1 version

[liberattgustavo]

Thanks : https://communities.vmware.com/t5/VMware-Workstation-Player/ubuntu-22-04-install-vm-workstation-error/td-p/2905277

This is what helped me

cd /usr/lib/vmware/modules/source
git clone https://github.com/mkubecek/vmware-host-modules
cd vmware-host-modules
git checkout workstation-16.2.3
make
tar -cf vmnet.tar vmnet-only
tar -cf vmmon.tar vmmon-only
mv vmnet.tar /usr/lib/vmware/modules/source/
mv vmmon.tar /usr/lib/vmware/modules/source/
vmware-modconfig --console --install-all

[Sgtkeebs]

Are we going to need to do this every time the kernel updates? Kind of frustrated I need my vms for research, and I may go back to 20.04 if we need to do this every time the kernel updates.

[liberattgustavo]

VMWare will use the same files to compile modules to the new kernel.

I've Upgraded the kernel from 5.15.0-25 to 5.15.0-27 and it still working without interference

[kapqa]

this happens also on Ubuntu 20.04 with newer Kernel 5.15,

fortunately the solution provided works also for 20.04;

[sacd7]

Thanks. This worked.

[jbrooksfrtw]

Confirmed. Fixed my issue as well. 

Thanks.

[altituded]

It still fails for me:

uname -a

Linux nuc11 5.13.0-40-generic #45~20.04.1-Ubuntu SMP Mon Apr 4 09:38:31 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a

No LSB modules are available.

Distributor ID: Ubuntu

Description: Ubuntu 20.04.4 LTS

Release: 20.04

Codename: focal

 

cd /usr/lib/vmware/modules/source
sudo git clone https://github.com/mkubecek/vmware-host-modules
cd vmware-host-modules
sudo git checkout workstation-16.2.3
sudo make
sudo tar -cf vmnet.tar vmnet-only
sudo tar -cf vmmon.tar vmmon-only
sudo mv vmnet.tar /usr/lib/vmware/modules/source/
sudo mv vmmon.tar /usr/lib/vmware/modules/source/
sudo vmware-modconfig --console --install-all

 

result:

 

  MODULEBUILDDIR= postbuild

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

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

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

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

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

Starting VMware services:

   Virtual machine monitor                                            failed

   Virtual machine communication interface                             done

   VM communication interface socket family                            done

   Virtual ethernet                                                   failed

   VMware Authentication Daemon                                        done

Unable to start services

[calebaum]

O meu ubuntu 22.04 funcionou!! Obrigado

 

[Austkwabs]

on pop-os you have to add sudo make install when you finish, thats what worked for me after following the instructions. thanks.

[altituded]

It just doesn't work

[Austkwabs]

 

cd /usr/lib/vmware/modules/source
sudo git clone https://github.com/mkubecek/vmware-host-modules
cd vmware-host-modules
sudo git checkout workstation-16.2.3
sudo make && sudo make install
sudo tar -cf vmnet.tar vmnet-only
sudo tar -cf vmmon.tar vmmon-only
sudo vmware-modconfig --console --install-all

in addition to this steps i copied vmmon and vmnet to /dev/

then i run the command (sudo vmware-modconfig --console --install-all) again as the original post solutions wasn't working. its working now. ps-my pop-os is new install so if your os has been running for long time you may have to dig deeper for solution or reinstall if you backup your important stuff. hope vmware comes out with new update that works out of the box. hope it helps.

[altituded]

Thanks for your help!l

i’ll gave up on VMware

[Angel_Diaz]

the Austkwabs solution of 04-30-2022 12:53 AM worked for me on an upgrade from Ubuntu 20.04 to 22.04

[Navix201110141]

Austkwabs solution has worked fine for me. Thanks.

[mekanic1]

Which specific files did you copy over?  Path?  The vmmon.tar or vmmon-only...etc

"in addition to this steps i copied vmmon and vmnet to /dev/"

[d1v3rg3ntFX]

This was a huge help, thanks for sharing!

[ebsf1]

I just posted in another thread, and apologies for being repetitive but I've been trying to get Player to work for six weeks and don't know what else to do.

The foregoing all have failed.  Player remains unable to open a VM.  Player installs.  It can install a VM from ISO and run it but the VM cannot be restarted using the VM's restart command, and cannot be opened after reboot.

What's been done:

• I have attempted this on Ubuntu 20.04 and three or four reinstalls of Ubuntu 22.04.
• I have attempted reinstall of VMware Player 16.2.3 fifteen or twenty times.
• I have attempted every one of the foregoing recommendations at least three times.

Please see attached logs.  Any suggestions that actually get the software working would be profoundly appreciated.

Attachment(s)

vmware-15873.log   36 KB 1 version

vmware-modconfig.txt   2 KB 1 version

[continuum]

Trying to repeat something that failed once several times usually does not make it better - on the contrary.
Please check if you really have install the kernel headers for your running kernel.
From the looks of it VMplayer has not yet been installed completely.
Whats is the result of
uname -a

Ulli

[ebsf1]

I have absolutely no idea what a kernel header is, how to check whether it/they is/are either installed or really installed, or how to either install or really install it/them.

 

What I have installed is Ubuntu Desktop 22.04, applying updates using aptitude.  If anything else is necessary, then obviously, the installer should do it.

 

Obviously, the problem is VMware Player hasn't been installed completely.  That's my point.  The installer installs the app, whereupon it fails.  The app continues to fail after applying the third-party kludge. The question is how to get it to install it fully, so it works.  One wonders if perhaps the developer might have an interest in there being a functional installer.

 

uname -a

 

returns:

 

Linux greystone 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

 

 

Two files are attached, one being STDOUT from executing the .bundle file.  I never have seen so many (or even any) error messages from vmware-installer.  These reference elementary syntax and dependency errors, which is both astonishing and alarming.  What also is inexplicable is that it concludes with a statement that the installation completed successfully when it obviously did not.

 

Also attached is the log file from the failed kludge attempt.

 

 

Any ideas about how to get the software installed and running would be greatly appreciated.

 

 

Attachment(s)

VMware-Player-Full-16.2.3-19376536.x86_64-STDOUT.txt   18 KB 1 version

vmware-3050.log   35 KB 1 version

[vitoie]

done this and managed to get the install running. stupid me did forgot to do other checks about the version and I have now corrupted it all. guess I will just reinstall everything from scratch and see how it goes

 

https://www.itzgeek.com/how-tos/linux/ubuntu-how-tos/how-to-install-vmware-workstation-16-pro-on-ubuntu-22-04-ubuntu-20-04.html

[Angel_Diaz]

Thanks, this worked for me on a new install of Ubuntu 22.04

[tdveira]

Thank my friend.

Works for me.

[UF2007]

Thanks,

excellent description for this work around. Saved me a lot of time

 

[izzycrow]

thank you so much for this!

[piete]

Thanks, this worked on Kubuntu 22.04

[VirtualBob]

Worked for me Thanks!!!

 

[gylka]

I don't want to sound negative and it's not directly on the topic, but why you (vmware) don't include this solution in your bundle?

This problem has been out in the open for months, and I remember solving it with this solution like a month and a half ago. Now I have to install it again on Kubuntu 22.04 and problem is still there with the latest bundle (installer).

And it's not the first time, over the last year or so it was always some issue where you have to find some hacky solution on your own forum that for some reason you didn't incorporate into your own installer.

Never had issues (I think ever for many-many years) with Windows version, but on Linux it's always reading forums, finding solutiuons, hacks, etc. The quality of Linux releases has been subpar for me. 

Again, sorry for a bit negative tone, it's just not the first time.

[continuum]

Last time I have seen one of the VMware Linux developers post in this forum was in 2007 if I remember right.
As far as I know VMware does not even have an option to file bugs for Workstation.

And just for your information - this forum may look like a forum driven by VMware Inc. all what VMware actually does here is provide the platform If you get help here you get this help from volunteers like me ....
>I don't want to sound negative and it's not directly on the topic, but why you (vmware) don't include this solution in your bundle?

Those that would know the answer to such a question simply dont come here

Ulli

[Vex3]

vmware going to provide an official fix?

[continuum]

Solutions for problems with "bleeding edge" distributions like Ubuntu 22 are provided by the Ubuntu scene - not by VMware Inc.
Look at the other posts about Ubuntu 22 + WS 16 - the solution has been posted several weeks/ months ago.

Ulli

[rfreytag]

I am running Ubuntu 20.04 LTS and seeing this problem repeatedly.  22.04 LTS and 20.04 LTS ahould be better supported.

 

[continuum]

The situation is still the same as it was in 2002.
Supported distributions install flawlessly.
Unsupported distributions install flawlessly once a smart user of distribution XY figured out how to patch the installer.
So we have 3 options:
1. demand that VMware fixes the problem and give up after one or two decades. Obviously this is not a solution orientated strategy and probably bad for your mental health.
2. accept the situation as it is and learn where to find the patches for your unsupported distribution.
3. switch to a supported distribution

Known side-effects of each approach:
1. folks start to kill the waiting time and start knitting - and we sure dont need to discuss the devastating results of picking up a hobby like knitting.
You will run out of wool every 4.53856 days and the kids will complain about scratchy pullovers.

2. live with getting the latest and maybe buggiest version ever just a few weeks later than the warrior-minded early adopters.
Major advantage - you will hear about the ugliest new bugs in advance and can make an educated decision before you start to change your current version

3. become a happy Debian user

Ulli

 

[louyo]

>>3. become a happy Debian user

Works for me

[continuum]

Once I realised that knitting would drive me crazy in the long run
I also switched from Ubuntu to Debian

 

[Technogeezer]

I don’t know if I would consider Ubuntu as “bleeding edge”. Rolling distributions give me more up to date packages than Ubuntu does. 
Ubuntu is more like bleeding to death by a thousand cuts. 

[gilig24853]

I install new version (16.2.4) and it works for me

https://customerconnect.vmware.com/downloads/details?downloadGroup=WKST-1624-LX&productId=1038

[Sgtkeebs]

 I was just about to post this that there was a new version released. So everything works good with 16.2.4?

[continuum]

read https://communities.vmware.com/t5/VMware-Workstation-Pro/VMware-engineers-and-documentation-authors/m-p/2918683#M176659

 

[Sgtkeebs]

I unfortunately do not see anything regarding how the new patch is working on 22.04, I mean from an end user perspective of installing and getting the kernel modules to compile.  

[continuum]

Then please complain in the other post - so that the Workstation product manager sees it.
Have you tried the patch from Michael Kubecek

[Sgtkeebs]

I am sorry miscommunication. I was at work and I don't have a readily available 22.04 system I can install VMware with the new patch, so I just want to know how others experience is that went through the workaround in April. I am not complaining about anything just want general feedback, but I am home now and can install it myself. 

[ebsf1]

16.2.4 fails in precisely the same way as 16.2.3 on Ubuntu 22.04, as far as I can tell, at least for Workstation Player.  I posted to this effect last evening.  The app simply cannot launch a guest.

 

This said, after months, I think I had a breakthrough today, which requires a synthesis of 5-7 separate hacks or deviations from commonly posted procedures.  I still need to confirm a few things but stay tuned.

[btsbrian]

 

My solution script, which works with my current kernel/PopOS! after the 16.2.4 still failed...

------

 

#!/bin/sh
wget https://github.com/mkubecek/vmware-host-modules/archive/workstation-16.2.4.tar.gz
tar -xzf workstation-16.2.4.tar.gz
cd vmware-host-modules-workstation-16.2.4
tar -cf vmmon.tar vmmon-only
tar -cf vmnet.tar vmnet-only
sudo cp -v vmmon.tar vmnet.tar /usr/lib/vmware/modules/source/
sudo vmware-modconfig --console --install-all

[tetsuo29a]

The "Second method (replace original tarballs)" method listed on this page worked for me on 22.04 with kernel 5.18.10-76051810-generic

https://github.com/mkubecek/vmware-host-modules/blob/master/INSTALL

[gylka]

Didn't use Wrokstation 16.2.3 for couple of months and ran again recently and had same error with recompiling vmmem/vmmon stuff (probably updates overwriten some changes, I don't know).

I saw that 16.2.4 is out, so I uninstalled 16.2.3 and installed 16.2.4 and it worked for me without this hackery on Kubuntu 22.04 (kernel 5.15.0-41). So I should probably say "finally!"