VMware 14.1.2 worked OK with Kernel 4.17, on my Fedora 28 test system, but after updating to 4.18-rc1 the following occurred:

Modules (vmmon/vmnet) compiled OK, but – after further testing – appeared to have a runtime problem..    I applied the vmmon patches from Michal Kubeček, at https://github.com/mkubecek/vmware-host-modules/commit/3f2a6c720f68 and this also compiled cleanly.

When I ran # vmware-modconfig …. I got the following ‘error’:

# vmware-modconfig --console --install-all
..........................
Received option outside of allowed bounds. Option was -1
........................
Must use a valid mode. Use one of:
............................

So, I tried a manual compile/install of vmmon and vmnet, into /lib/modules/4.18.0-rc1/misc (after creating the ~/misc sub-directory), and then #depmod -a and # modprobe vmmon  # modprobe vmnet..

But then:

# service vmware start
Starting vmware (via systemctl): Job for vmware.service failed because the control process exited with error code.
See "systemctl status vmware.service" and "journalctl -xe" for details.
                                               [FAILED]

and:

# systemctl status vmware.service
● vmware.service - SYSV: This service starts and stops VMware services
Loaded: loaded (/etc/rc.d/init.d/vmware; generated)
Active: failed (Result: exit-code) since Mon 2018-06-18 01:02:04 PDT; 3min 7s ago
Docs: man:systemd-sysv-generator(8)
Process: 5663 ExecStart=/etc/rc.d/init.d/vmware start (code=exited, status=1/FAILURE)
CGroup: /system.slice/vmware.service
├─3879 /usr/bin/vmnet-bridge -s 6 -d /var/run/vmnet-bridge-0.pid -n 0
├─3933 /usr/bin/vmnet-netifup -s 6 -d /var/run/vmnet-netifup-vmnet1.pid /dev/vmnet1 vmnet1
├─3953 /usr/bin/vmnet-dhcpd -s 6 -cf /etc/vmware/vmnet1/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet1/dhcpd/dhcpd.leases -pf /var/>
├─3964 /usr/bin/vmnet-natd -s 6 -m /etc/vmware/vmnet8/nat.mac -c /etc/vmware/vmnet8/nat/nat.conf
├─3969 /usr/bin/vmnet-netifup -s 6 -d /var/run/vmnet-netifup-vmnet8.pid /dev/vmnet8 vmnet8
├─3985 /usr/bin/vmnet-dhcpd -s 6 -cf /etc/vmware/vmnet8/dhcpd/dhcpd.conf -lf /etc/vmware/vmnet8/dhcpd/dhcpd.leases -pf /var/>
└─4025 /usr/sbin/vmware-authdlauncher

Jun 18 01:02:03 rgtest vmware[5663]: Blocking file system[FAILED]
Jun 18 01:02:04 rgtest vmware[5663]: Virtual ethernet[ OK ]
Jun 18 01:02:04 rgtest vmware[5663]: VMware Authentication Daemon[ OK ]
Jun 18 01:02:04 rgtest systemd[1]: vmware.service: Control process exited, code=exited status=1
Jun 18 01:02:04 rgtest systemd[1]: vmware.service: Failed with result 'exit-code'.
Jun 18 01:02:04 rgtest systemd[1]: Failed to start SYSV: This service starts and stops VMware services.

The userland # vmware command did nothing, and just returned to a command prompt..

After more testing, I found that using the # /usr/lib/vmware/bin/vmware start command actually worked, and resulted in the normal VMware graphical window appearing, and guest o/s (WinXP, and Fedora) started OK, and guest networking seemed to work correctly..

So..  It would appear that the various error messages are somewhat confused, and VMware does actually work, although not in the normal way..

Robert Gadsdon.   June 18, 2018