Problem
Building of vmnet module fails in newer kernel versions. For me it failed in kernel version 6.4.10-arch1-1. (Yes I use Archlinux)
I compiled with:
vmware-modconfig --console --install-all
I got:
/tmp/modconfig-7XKYCP/vmnet-only/bridge.c: In function ‘VNetBridgeSendLargePacket’:
/tmp/modconfig-7XKYCP/vmnet-only/bridge.c:1413:11: error: implicit declaration of function ‘skb_gso_segment’; did you mean ‘tcp_gso_segment’? [-Werror=implicit-function-declaration]
1413 | segs = skb_gso_segment(skb, 0);
| ^~~~~~~~~~~~~~~
| tcp_gso_segment
/tmp/modconfig-7XKYCP/vmnet-only/bridge.c:1413:9: warning: assignment to ‘struct sk_buff *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
1413 | segs = skb_gso_segment(skb, 0);
| ^
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:252: /tmp/modconfig-7XKYCP/vmnet-only/bridge.o] Error 1
make[1]: *** [Makefile:2032: /tmp/modconfig-7XKYCP/vmnet-only] Error 2
make: *** [Makefile:117: vmnet.ko] Error 2
make: Leaving directory '/tmp/modconfig-7XKYCP/vmnet-only'
Unable to install all modules. See log for details.
Analysis
I figured out that in Linux kernel commit https://github.com/torvalds/linux/commit/d457a0e329b0bfd3a1450e0b1a18cd2b47a25a08 there was a change.
They moved code (including the function skb_gso_segment) from one "header" to another (<linux/inetdevice.h> to <net/gso.h>).
Commit message: "Move declarations into include/net/gso.h and code into net/core/gso.c"
Solution
In bridge.c one needs to add #include <net/gso.h>
How? I bet You are lazy... Assuming You have installed the .bundle and just want to compile... Try this:
# Cd to te dir where the vmware modules are.
cd /usr/lib/vmware/modules/source
# Unpack vmnet.
tar -xvf vmnet.tar
# Add the missing include (code is just there now)
sed -i '46 a#include <net/gso.h>' vmnet-only/bridge.c
# Backup original vmnet.tar
mv vmnet.tar vmnet.tar.original
# Pack the patched vmnet.
tar -cf vmnet.tar vmnet-only
Now if you are running
vmware-modconfig --console --install-all
again everything should work.
Disclaimer
Since it is a real pain to let You vmware guys know of a bug. I at least try to help people here. I couldn't figure a way to send You this...
Hope this helps 
It seemed it worked initially, but when starting the VM, the error popped out
[are@work-st source]$ cat /etc/redhat-release
Fedora release 38 (Thirty Eight)
[are@work-st source]$ uname -a
Linux work-st 6.4.15-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Sep 7 00:25:01 UTC 2023 x86_64 GNU/Linux
Could not open /dev/vmmon: No such file or directory.
Please make sure that the kernel module `vmmon' is loaded.
sudo systemctl status vmware.service
[sudo] password for are:
× vmware.service - VMware host virtualization and network services for Workstation
Loaded: loaded (/usr/lib/systemd/system/vmware.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Sun 2023-09-17 08:10:29 BST; 7min ago
Process: 29915 ExecStart=/usr/lib/vmware/scripts/init/vmware start (code=exited, status=203/EXEC)
CPU: 1ms
Sep 17 08:10:29 work-st (vmware)[29915]: vmware.service: Failed to locate executable /usr/lib/vmware/scripts/init/vmware: No such file or directory
Sep 17 08:10:29 work-st (vmware)[29915]: vmware.service: Failed at step EXEC spawning /usr/lib/vmware/scripts/init/vmware: No such file or directory
Sep 17 08:10:29 work-st systemd[1]: Starting vmware.service - VMware host virtualization and network services for Workstation...
Sep 17 08:10:29 work-st systemd[1]: vmware.service: Control process exited, code=exited, status=203/EXEC
Sep 17 08:10:29 work-st systemd[1]: vmware.service: Failed with result 'exit-code'.
Sep 17 08:10:29 work-st systemd[1]: Failed to start vmware.service - VMware host virtualization and network services for Workstation.[are@work-st source]$ sudo systemctl status vmware.service
[sudo] password for are:
× vmware.service - VMware host virtualization and network services for Workstation
Loaded: loaded (/usr/lib/systemd/system/vmware.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Sep 17 08:10:29 work-st systemd[1]: vmware.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit vmware.service has entered the 'failed' state with result 'exit-code'.
Sep 17 08:10:29 work-st systemd[1]: Failed to start vmware.service - VMware host virtualization and network services for Workstation.
░░ Subject: A start job for unit vmware.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit vmware.service has finished with a failure.
░░
░░ The job identifier is 5145 and the job result is failed.
I have lost a number of months for how long I can't use VMware workstation.
