I was trying to post a question/topic in Forums more or less on this topic but on VMWare Player – I’ve posted in the past but seem to forgotten how. There is nothing that says “New Topic” or something – there might well be but I could not find it.
Basically, it is a question / suggestion. Yes I know Rocky Linux is a bug-for-bug copy of RHEL 8.x, but this seems to be an OLD bug: I have been trying to install VMware Player 16.1.2 in Rocky Linux 8.4. It Blows up. So I then tried installing VMware Player 15.5.7, it too blew up with the same problem, so I dropped back to 15.5.0, it too blew up, so I dropped back to 15.1.0, and I at last got to the point where I got the lic. agreement, and the rest of the install, but then when it came to the actual start up of the program it too blew up; same with 15.0.4, and 15.0.0. VMware Player 14.1.7 gives you an error right out the gate.
What do I mean by “Blows up”? You do the install, you get a whole lot of chafe, it then says “Installing VMware Player 16.1.2, followed by “Configuring”, followed by a lot of RailRoad tracks (#####), then it says “Installation was Successful”. “GREAT” you think. You then go and start up VMware. You click on the icon, and you get the familiar, “Before you can run VMware, several modules must be complied and loaded into the running kernel”. It then asks you if you wish to install. You click on install, and then it says it needs " Authentication is needed” and to “please enter your Root Password”, you do so and then… BOOM!! You then get this cheery message:
" Unable to install all modules. See log /tmp/vmware-[user]/vmware-[number].log for details. (Exit code 1)"
Everything from 15.5.0 and above you get this message. Everything from 15.0.0 to 15.1.0 gives you the lic. agreement etc., but then terminates in the “(Exit code 1)” message.
I did enough research and this seems to be a specific bug that is restricted to RHEL 8.x, CentOS 8.x, and of course, Rocky Linux 8.4. The bug *does not" affect RHEL 7.9, or affect CentOS 7.9 (I have VMWare Player 16.1.2 running on CentOS 7.9). The bug also does not affect openSUSE 15.3 Leap which I am running on a separate drive.
Is there any way someone could fix this bug, and/or in the alternative come up with a work-around?
One last thing: I would be greatly appreciate it if someone can tell me HOW to post a New topic. I can not find anything that says “New Topic” or something to that effect.