{"id":2322,"date":"2018-06-18T01:46:54","date_gmt":"2018-06-18T08:46:54","guid":{"rendered":"http:\/\/rglinuxtech.com\/?p=2322"},"modified":"2018-06-18T01:46:54","modified_gmt":"2018-06-18T08:46:54","slug":"vmware-odd-behaviour-with-kernel-4-18-rc1-and-a-workaround","status":"publish","type":"post","link":"https:\/\/rglinuxtech.com\/?p=2322","title":{"rendered":"VMware – Odd Behaviour with Kernel 4.18-rc1, and a Workaround?"},"content":{"rendered":"

VMware 14.1.2 worked OK with Kernel 4.17, on my Fedora 28 test system, but after updating to 4.18-rc1<\/strong> the following occurred:<\/p>\n

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

When I ran # vmware-modconfig ….<\/span><\/strong> I got the following ‘error’:<\/p>\n

# vmware-modconfig --console --install-all<\/strong><\/span>\r\n..........................<\/strong><\/span>\r\nReceived option outside of allowed bounds. Option was -1<\/strong><\/span>\r\n........................<\/strong><\/span>\r\nMust use a valid mode. Use one of:<\/strong><\/span>\r\n............................<\/strong><\/span><\/pre>\n
So, I tried a manual compile\/install of vmmon<\/em> and vmnet<\/em>, into \/lib\/modules\/4.18.0-rc1\/misc<\/strong><\/span> (after creating the ~\/misc sub-directory), and then #depmod -a<\/span><\/strong><\/code> and # modprobe vmmon<\/span><\/strong><\/code>\u00a0 # modprobe vmnet<\/strong><\/span><\/code>..<\/p>\n
But then:<\/p>\n
# service vmware start<\/strong><\/span>\r\nStarting vmware (via systemctl): Job for vmware.service failed because the control process exited with error code.<\/strong><\/span>\r\nSee \"systemctl status vmware.service\" and \"journalctl -xe\" for details.<\/strong><\/span>\r\n                                               [FAILED]<\/strong><\/span><\/pre>\n
and:<\/p>\n
# systemctl status vmware.service<\/strong><\/span>\r\n\u25cf vmware.service - SYSV: This service starts and stops VMware services<\/strong><\/span>\r\nLoaded: loaded (\/etc\/rc.d\/init.d\/vmware; generated)<\/strong><\/span>\r\nActive: failed (Result: exit-code) since Mon 2018-06-18 01:02:04 PDT; 3min 7s ago<\/strong><\/span>\r\nDocs: man:systemd-sysv-generator(8)<\/strong><\/span>\r\nProcess: 5663 ExecStart=\/etc\/rc.d\/init.d\/vmware start (code=exited, status=1\/FAILURE)<\/strong><\/span>\r\nCGroup: \/system.slice\/vmware.service<\/strong><\/span>\r\n\u251c\u25003879 \/usr\/bin\/vmnet-bridge -s 6 -d \/var\/run\/vmnet-bridge-0.pid -n 0<\/strong><\/span>\r\n\u251c\u25003933 \/usr\/bin\/vmnet-netifup -s 6 -d \/var\/run\/vmnet-netifup-vmnet1.pid \/dev\/vmnet1 vmnet1<\/strong><\/span>\r\n\u251c\u25003953 \/usr\/bin\/vmnet-dhcpd -s 6 -cf \/etc\/vmware\/vmnet1\/dhcpd\/dhcpd.conf -lf \/etc\/vmware\/vmnet1\/dhcpd\/dhcpd.leases -pf \/var\/><\/strong><\/span>\r\n\u251c\u25003964 \/usr\/bin\/vmnet-natd -s 6 -m \/etc\/vmware\/vmnet8\/nat.mac -c \/etc\/vmware\/vmnet8\/nat\/nat.conf<\/strong><\/span>\r\n\u251c\u25003969 \/usr\/bin\/vmnet-netifup -s 6 -d \/var\/run\/vmnet-netifup-vmnet8.pid \/dev\/vmnet8 vmnet8<\/strong><\/span>\r\n\u251c\u25003985 \/usr\/bin\/vmnet-dhcpd -s 6 -cf \/etc\/vmware\/vmnet8\/dhcpd\/dhcpd.conf -lf \/etc\/vmware\/vmnet8\/dhcpd\/dhcpd.leases -pf \/var\/><\/strong><\/span>\r\n\u2514\u25004025 \/usr\/sbin\/vmware-authdlauncher<\/strong><\/span>\r\n\r\nJun 18 01:02:03 rgtest vmware[5663]: Blocking file system[FAILED]<\/strong><\/span>\r\nJun 18 01:02:04 rgtest vmware[5663]: Virtual ethernet[ OK ]<\/strong><\/span>\r\nJun 18 01:02:04 rgtest vmware[5663]: VMware Authentication Daemon[ OK ]<\/strong><\/span>\r\nJun 18 01:02:04 rgtest systemd[1]: vmware.service: Control process exited, code=exited status=1<\/strong><\/span>\r\nJun 18 01:02:04 rgtest systemd[1]: vmware.service: Failed with result 'exit-code'.<\/strong><\/span>\r\nJun 18 01:02:04 rgtest systemd[1]: Failed to start SYSV: This service starts and stops VMware services.<\/strong><\/span><\/pre>\n
The userland # vmware<\/strong><\/span><\/code> command did nothing, and just returned to a command prompt..<\/p>\n
After more testing, I found that using the # \/usr\/lib\/vmware\/bin\/vmware start<\/code><\/strong><\/span> 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..<\/p>\n
So..\u00a0 It would appear that the various error messages are somewhat confused, and VMware does actually work, although not<\/span> in the normal way..<\/p>\n
Robert Gadsdon.\u00a0\u00a0 June 18, 2018<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"
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..\u00a0\u00a0\u00a0 I applied the vmmon patches from Michal Kube\u010dek, at https:\/\/github.com\/mkubecek\/vmware-host-modules\/commit\/3f2a6c720f68 and this also compiled cleanly. When I ran # vmware-modconfig …<\/span> Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[5,10,1238,11,14,15,19,1533,25],"tags":[1898,1903,1904,401,1902,418],"class_list":["post-2322","post","type-post","status-publish","format-standard","hentry","category-compilation","category-fedora","category-fix","category-hacks","category-kernel","category-linux-2","category-opinion","category-patches","category-vmware","tag-kernel-4-18-rc1","tag-runtime-problems","tag-userland","tag-vmmon-patch","tag-vmware-14-1-2","tag-workaround"],"_links":{"self":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/2322","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2322"}],"version-history":[{"count":2,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/2322\/revisions"}],"predecessor-version":[{"id":2324,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/2322\/revisions\/2324"}],"wp:attachment":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2322"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2322"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2322"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}