VMware Communities
MickOhrberg
Contributor
Contributor

VMware Workstation 8 and Fedora 19/kernel 3.10.3, vmnet issues

I apologize if this has been covered - I was not able to find a discussion with a solution that works for me. Basically, per the subject, I have a 64-bit Fedora 19 machine with kernel 3.10.3 and VMware Workstation 8. Following the instructions at https://wiki.archlinux.org/index.php/VMware#3.10_kernels VMblock builds fine, but VMnet still fails:

2013-08-02T08:13:07.738-06:00| vthread-3| I120: Building module vmnet.

2013-08-02T08:13:07.739-06:00| vthread-3| I120: Extracting the sources of the vmnet module.

2013-08-02T08:13:07.760-06:00| vthread-3| I120: Building module with command: /bin/make -j -C /tmp/vmware-root/modules/vmnet-only auto-build SUPPORT_SMP=1 HEADER_DIR=/lib/modules/3.10.3-300.fc19.x86_64/build/include CC=/bin/gcc GREP=/bin/make IS_GCC_3=no VMCCVER=4.8.1

2013-08-02T08:13:09.604-06:00| vthread-3| I120: Failed to compile module vmnet

Some more detailed logs are:

[ ... ]

/usr/lib/vmware/modules/source/vmnet-only/netif.c: In function ‘VNetNetIf_Create’:

/usr/lib/vmware/modules/source/vmnet-only/netif.c:250:4: error: implicit declaration of function ‘VNetProc_MakeEntry’ [-Werror=implicit-function-declaration]

    retval = VNetProc_MakeEntry(netIf->port.jack.name, S_IFREG,

    ^

/usr/lib/vmware/modules/source/vmnet-only/netif.c:260:33: error: dereferencing pointer to incomplete type

       netIf->port.jack.procEntry->read_proc = VNetNetIfProcRead;

                                 ^

/usr/lib/vmware/modules/source/vmnet-only/netif.c:260:47: error: ‘VNetNetIfProcRead’ undeclared (first use in this function)

       netIf->port.jack.procEntry->read_proc = VNetNetIfProcRead;

                                               ^

/usr/lib/vmware/modules/source/vmnet-only/netif.c:260:47: note: each undeclared identifier is reported only once for each function it appears in

/usr/lib/vmware/modules/source/vmnet-only/netif.c:261:33: error: dereferencing pointer to incomplete type

       netIf->port.jack.procEntry->data = netIf;

                                 ^

/usr/lib/vmware/modules/source/vmnet-only/netif.c: In function ‘VNetNetIfProcRead’:

/usr/lib/vmware/modules/source/vmnet-only/netif.c:671:4: warning: passing argument 2 of ‘VNetPrintPort’ from incompatible pointer type [enabled by default]

    len += VNetPrintPort(&netIf->port, page+len);

    ^

In file included from /usr/lib/vmware/modules/source/vmnet-only/netif.c:42:0:

/usr/lib/vmware/modules/source/vmnet-only/vnetInt.h:201:6: note: expected ‘struct seq_file *’ but argument is of type ‘char *’

void VNetPrintPort(const VNetPort *port, struct seq_file *seqf);

      ^

/usr/lib/vmware/modules/source/vmnet-only/netif.c:671:4: error: void value not ignored as it ought to be

    len += VNetPrintPort(&netIf->port, page+len);

    ^

cc1: some warnings being treated as errors

make[2]: *** [/usr/lib/vmware/modules/source/vmnet-only/netif.o] Error 1

make[1]: *** [_module_/usr/lib/vmware/modules/source/vmnet-only] Error 2

make[1]: Leaving directory `/usr/src/kernels/3.10.3-300.fc19.x86_64'

make: *** [vmnet.ko] Error

A developer I am not, so I'm sort of lost as to what exactly is causing the issue, but there appears to be something in the file netif.c Smiley Wink

Thank you in advance for any help.

0 Kudos
5 Replies
mfelker
Expert
Expert

Have a look at this:

https://wiki.archlinux.org/index.php/VMware

Ths stuff worked for using  WS 9 on Ubuntu 13.10 and openSUSE 13.1.  Its worth a try.  Make sure you COMPLETELY remove WS before applying any patch.

0 Kudos
WoodyZ
Immortal
Immortal

mfelker wrote: Have a look at this: https://wiki.archlinux.org/index.php/VMware

The link you provided is to the same page that the link in the OP point to! Smiley Wink  Additionally the OP is using WS 8 not WS 9 and he already tried what was on the linked page with WS 8 and it, not surprisingly, didn't work as I'm sure there are code changes in the modules between the two version that require different patching.

0 Kudos
mfelker
Expert
Expert

Yeah.   Well I did say that the Archlinux programmer indicated it was for WS 9 but my experience with patches to WS before shows  that sometimes they will work with earlier versions of WS.  Most likely WS 8 can't install on Fedora 19.

He might try an extensive search on Google or just uninstall it and try WS 10 TP.  Not sure if anybody has gotten that to install on FC 19 either.

0 Kudos
raven009
Contributor
Contributor

Hi Mick,

I succesfully built all modules. Very helpful for me was original patch.

I'm running 3.10.9-200.fc19.x86_64 and VMware 8.0.6.

You need to fix netif.c (during patching you can notice that patching of that file failed).

Hopefully I remember well what I did:

1. remove this part:

} else {

- netIf->port.jack.procEntry->read_proc = VNetNetIfProcRead;

- netIf->port.jack.procEntry->data = netIf;

2. and remove this function:  * VNetNetIfProcRead -- at the end of file.

Also you need to patch vmblock.tar and finally you need patch vmci.tar ( I used this link: Linux Kernel 3.8.* – VMware failed to build vmci | u wot? )

On my laptop vmware service was available after reboot.

Wish you good luck

0 Kudos
MickOhrberg
Contributor
Contributor

raven009 wrote:

Hi Mick,

I succesfully built all modules. Very helpful for me was original patch.

I'm running 3.10.9-200.fc19.x86_64 and VMware 8.0.6.

You need to fix netif.c (during patching you can notice that patching of that file failed).

Hopefully I remember well what I did:

1. remove this part:

} else {

- netIf->port.jack.procEntry->read_proc = VNetNetIfProcRead;

- netIf->port.jack.procEntry->data = netIf;

2. and remove this function:  * VNetNetIfProcRead -- at the end of file.

Also you need to patch vmblock.tar and finally you need patch vmci.tar ( I used this link: Linux Kernel 3.8.* – VMware failed to build vmci | u wot? )

On my laptop vmware service was available after reboot.

Wish you good luck

Awesome - I will give this a try! The latest VMplayer runs without issue, so I've been using it as workaround, but this should let me get back to VMware Workstation - thanks!

0 Kudos