my os is archlinux and kernel is 6.3.7-arch1-1, install vmware-workstation form AUR, but start vmware-network failed
vmware-networks.service - VMware Networks
Loaded: loaded (/usr/lib/systemd/system/vmware-networks.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Wed 2023-06-14 12:47:38 CST; 9min ago
Process: 5592 ExecStartPre=/sbin/modprobe vmnet (code=killed, signal=SEGV)
Process: 5597 ExecStart=/usr/bin/vmware-networks --start (code=exited, status=1/FAILURE)
CPU: 47ms
6月 14 12:47:38 timelu vmware-networks[5597]: Failed to start NAT service on vmnet8
6月 14 12:47:38 timelu vmware-networks[5597]: Failed to enable hostonly virtual adapter on vmnet8
6月 14 12:47:38 timelu vmnet-dhcpd[5651]: exiting.
6月 14 12:47:38 timelu vmware-networks[5597]: Failed to start DHCP service on vmnet8
6月 14 12:47:38 timelu vmware-networks[5597]: Failed to start some/all services
6月 14 12:47:38 timelu vmware-networks[5597]: Started Bridge networking on vmnet0
6月 14 12:47:38 timelu systemd[1]: vmware-networks.service: Control process exited, code=exited, status
6月 14 12:47:38 timelu vmnetBridge[5615]: Bridge process exiting.
6月 14 12:47:38 timelu systemd[1]: vmware-networks.service: Failed with result 'exit-code'.
6月 14 12:47:38 timelu systemd[1]: Failed to start VMware Networks.
and see kernel bug happend when modprobe vmnet
I have the same issue on OpenSUSE Tumbleweed after installing Kernel 6.3.7
If I revert there is no issue
I encountered the same problem with kernel 6.3.7 on Fedora 38, reverting back to 6.2.9 got things back working.
Sounds like we need to wait for VMware to patch.
I can also confirm as of 17.0.2 build-21581411 which is the latest this DOES NOT work if you have the new kernel.
I found this, which MAY be a possible workaround, but not sure I want to try it since right now things are fine if I just wait to update.