{"id":1008,"date":"2014-01-20T14:26:36","date_gmt":"2014-01-20T14:26:36","guid":{"rendered":"http:\/\/rglinuxtech.com\/?p=1008"},"modified":"2014-01-20T14:26:36","modified_gmt":"2014-01-20T14:26:36","slug":"3-13-final-and-a-vmware-patch-you-may-not-need","status":"publish","type":"post","link":"https:\/\/rglinuxtech.com\/?p=1008","title":{"rendered":"3.13 Final – And a VMware Patch You May Not Need.."},"content":{"rendered":"

Installed 3.13 Final<\/strong> on my test system, and then on my main system, and encountered an odd problem with VMware (10.0.1)..<\/p>\n

On my test<\/strong><\/em> system, VMware had been compiling and installing\/running OK on all the 3.13-rc versions, and 3.13 Final, but on my main<\/strong><\/em> system, vmnet<\/strong> failed to compile:<\/p>\n

...<\/strong>\r\n\/tmp\/modconfig-I1rVjt\/vmnet-only\/filter.c:206:1: error: conflicting types for \u2018VNetFilterHookFn\u2019<\/strong>\r\n\u00a0VNetFilterHookFn(unsigned int hooknum,\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/\/ IN:<\/strong>\r\n\u00a0^<\/strong>\r\n\/tmp\/modconfig-I1rVjt\/vmnet-only\/filter.c:64:18: note: previous declaration of \u2018VNetFilterHookFn\u2019 was here<\/strong>\r\n\u00a0static nf_hookfn VNetFilterHookFn;<\/strong>\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ^<\/strong>\r\n\/tmp\/modconfig-I1rVjt\/vmnet-only\/filter.c:64:18: warning: \u2018VNetFilterHookFn\u2019 used but never defined [enabled by default]<\/strong>\r\n\/tmp\/modconfig-I1rVjt\/vmnet-only\/filter.c:206:1: warning: \u2018VNetFilterHookFn\u2019 defined but not used [-Wunused-function]<\/strong>\r\n\u00a0VNetFilterHookFn(unsigned int hooknum,\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/\/ IN:<\/strong>\r\n\u00a0^<\/strong>\r\nmake[2]: *** [\/tmp\/modconfig-I1rVjt\/vmnet-only\/filter.o] Error 1<\/strong>\r\n..........<\/pre>\n
After some further research, it turned out that the reason for this inconsistency was that I had Netfilter<\/strong><\/em> selected with the kernel compilation options on my ‘main’ system, but not<\/span> on my ‘test’ system:
\nNetworking Support \/ Networking Options \/ Network packet filtering framework (Netfilter)<\/em><\/strong><\/p>\n
If you do<\/span> have Netfilter selected and compiled in, then the vmnet compile will fail, and there is a patch here:<\/p>\n
http:\/\/pastebin.com\/p3bkbAMu<\/p>\n
This patch has the correct changes, but – on my system – it failed to install, with a ‘malformed patch<\/em>‘ error..\u00a0\u00a0 I just manually edited the filter.c<\/strong> file, to make the changes shown in the patch, and everything worked OK..\u00a0\u00a0\u00a0 You may find that you have to reboot for the vmware modules to (re)load..<\/p>\n
So – to summarise..\u00a0\u00a0 If you have Netfilter<\/strong><\/em> selected in your kernel compilation – or you are using a ‘distro’ version of kernel 3.13 (which tend to have ‘everything’ selected) then you will need the patch.\u00a0\u00a0\u00a0 If you compile your own kernel, and don’t have Netfilter selected, then you won’t need the patch.<\/p>\n
I applied the changes to both my ‘test’ and ‘main’ systems (with Netfilter selected\/deselected) and VMware compiles and loads OK, now.<\/p>\n
For NVIDIA<\/strong>, the patch mentioned in the 3.13-rc articles is still needed, and both 319.82 and 331.38 – patched – install and run OK with 3.13 Final.<\/p>\n
Robert Gadsdon.\u00a0\u00a0 January 20, 2014.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"
Installed 3.13 Final on my test system, and then on my main system, and encountered an odd problem with VMware (10.0.1).. On my test system, VMware had been compiling and installing\/running OK on all the 3.13-rc versions, and 3.13 Final, but on my main system, vmnet failed to compile: … \/tmp\/modconfig-I1rVjt\/vmnet-only\/filter.c:206:1: error: conflicting types for \u2018VNetFilterHookFn\u2019 \u00a0VNetFilterHookFn(unsigned …<\/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,"footnotes":""},"categories":[5,11,14,15,18,19,20,25],"tags":[762,757,760,440,143,722,277,296,305,1175,761,402,763],"class_list":["post-1008","post","type-post","status-publish","format-standard","hentry","category-compilation","category-hacks","category-kernel","category-linux-2","category-nvidia","category-opinion","category-performance-2","category-vmware","tag-10-0-1","tag-319-82","tag-331-38","tag-compile-fail","tag-error","tag-kernel-3-13","tag-nvidia-2","tag-patch","tag-problem","tag-success","tag-vmnet","tag-vmware-2","tag-vnetfilterhookfn"],"_links":{"self":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1008","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=1008"}],"version-history":[{"count":1,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1008\/revisions"}],"predecessor-version":[{"id":1009,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/1008\/revisions\/1009"}],"wp:attachment":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1008"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1008"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1008"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}