VMware Communities
bigfeetliu
Contributor
Contributor

vmware-tools does not work in fedora11

I installed fedora11 with vmware fusion 2.0.4

but vmware-tools seem do not work, at least no shared-folders appear under /mnt/hgfs!!!!

I rechecked vmware-tools install procedures. it reported errors while run vmware-config-tools.pl:

-


Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config5/vmmemctl-only'

make -C /lib/modules/2.6.29.4-167.fc11.i686.PAE/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.29.4-167.fc11.i686.PAE'

CC /tmp/vmware-config5/vmmemctl-only/backdoorGcc32.o

In file included from /tmp/vmware-config5/vmmemctl-only/backdoor.h:29,

from /tmp/vmware-config5/vmmemctl-only/backdoorGcc32.c:45:

/tmp/vmware-config5/vmmemctl-only/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined

CC /tmp/vmware-config5/vmmemctl-only/os.o

In file included from /tmp/vmware-config5/vmmemctl-only/os.c:51:

/tmp/vmware-config5/vmmemctl-only/compat_wait.h:78: error: conflicting types for ‘poll_initwait’

include/linux/poll.h:67: note: previous declaration of ‘poll_initwait’ was here

make[2]: *** Error 1

make[1]: *** Error 2

make[1]: Leaving directory `/usr/src/kernels/2.6.29.4-167.fc11.i686.PAE'

make: *** http://vmmemctl.ko Error 2

make: Leaving directory `/tmp/vmware-config5/vmmemctl-only'

Unable to build the vmmemctl module.

-


Building the vmhgfs module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config6/vmhgfs-only'

make -C /lib/modules/2.6.29.4-167.fc11.i686.PAE/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.29.4-167.fc11.i686.PAE'

CC /tmp/vmware-config6/vmhgfs-only/backdoor.o

In file included from /tmp/vmware-config6/vmhgfs-only/backdoor.h:29,

from /tmp/vmware-config6/vmhgfs-only/backdoor.c:40:

/tmp/vmware-config6/vmhgfs-only/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined

CC /tmp/vmware-config6/vmhgfs-only/backdoorGcc32.o

In file included from /tmp/vmware-config6/vmhgfs-only/backdoor.h:29,

from /tmp/vmware-config6/vmhgfs-only/backdoorGcc32.c:45:

/tmp/vmware-config6/vmhgfs-only/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined

CC /tmp/vmware-config6/vmhgfs-only/bdhandler.o

In file included from /tmp/vmware-config6/vmhgfs-only/rpcout.h:30,

from /tmp/vmware-config6/vmhgfs-only/hgfsBd.h:28,

from /tmp/vmware-config6/vmhgfs-only/bdhandler.c:45:

/tmp/vmware-config6/vmhgfs-only/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined

In file included from /tmp/vmware-config6/vmhgfs-only/request.h:35,

from /tmp/vmware-config6/vmhgfs-only/bdhandler.c:50:

/tmp/vmware-config6/vmhgfs-only/compat_wait.h:78: error: conflicting types for ‘poll_initwait’

include/linux/poll.h:67: note: previous declaration of ‘poll_initwait’ was here

make[2]: *** Error 1

make[1]: *** Error 2

make[1]: Leaving directory `/usr/src/kernels/2.6.29.4-167.fc11.i686.PAE'

make: *** http://vmhgfs.ko Error 2

make: Leaving directory `/tmp/vmware-config6/vmhgfs-only'

Unable to build the vmhgfs module.

-


Building the vmxnet module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config7/vmxnet-only'

make -C /lib/modules/2.6.29.4-167.fc11.i686.PAE/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.29.4-167.fc11.i686.PAE'

CC /tmp/vmware-config7/vmxnet-only/vmxnet.o

In file included from /tmp/vmware-config7/vmxnet-only/vmxnet.c:48:

/tmp/vmware-config7/vmxnet-only/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined

/tmp/vmware-config7/vmxnet-only/vmxnet.c: In function ‘vmxnet_change_mtu’:

/tmp/vmware-config7/vmxnet-only/vmxnet.c:193: error: ‘struct net_device’ has no member named ‘priv’

/tmp/vmware-config7/vmxnet-only/vmxnet.c: In function ‘vmxnet_get_drvinfo’:

/tmp/vmware-config7/vmxnet-only/vmxnet.c:267: error: ‘struct net_device’ has no member named ‘priv’

/tmp/vmware-config7/vmxnet-only/vmxnet.c: In function ‘vmxnet_set_tso’:

/tmp/vmware-config7/vmxnet-only/vmxnet.c:305: error: ‘struct net_device’ has no member named ‘priv’

/tmp/vmware-config7/vmxnet-only/vmxnet.c: In function ‘vmxnet_link_check’:

/tmp/vmware-config7/vmxnet-only/vmxnet.c:659: error: ‘struct net_device’ has no member named ‘priv’

/tmp/vmware-config7/vmxnet-only/vmxnet.c: In function ‘vmxnet_probe_device’:

/tmp/vmware-config7/vmxnet-only/vmxnet.c:841: error: ‘struct net_device’ has no member named ‘priv’

/tmp/vmware-config7/vmxnet-only/vmxnet.c: In function ‘vmxnet_remove_device’:

/tmp/vmware-config7/vmxnet-only/vmxnet.c:1142: error: ‘struct net_device’ has no member named ‘priv’

/tmp/vmware-config7/vmxnet-only/vmxnet.c: In function ‘vmxnet_init_ring’:

/tmp/vmware-config7/vmxnet-only/vmxnet.c:1213: error: ‘struct net_device’ has no member named ‘priv’

/tmp/vmware-config7/vmxnet-only/vmxnet.c: In function ‘vmxnet_open’:

/tmp/vmware-config7/vmxnet-only/vmxnet.c:1338: error: ‘struct net_device’ has no member named ‘priv’

/tmp/vmware-config7/vmxnet-only/vmxnet.c: In function ‘check_tx_queue’:

/tmp/vmware-config7/vmxnet-only/vmxnet.c:1594: error: ‘struct net_device’ has no member named ‘priv’

/tmp/vmware-config7/vmxnet-only/vmxnet.c: In function ‘vmxnet_tx’:

/tmp/vmware-config7/vmxnet-only/vmxnet.c:1658: error: ‘struct net_device’ has no member named ‘priv’

/tmp/vmware-config7/vmxnet-only/vmxnet.c: In function ‘vmxnet_rx’:

/tmp/vmware-config7/vmxnet-only/vmxnet.c:2057: error: ‘struct net_device’ has no member named ‘priv’

/tmp/vmware-config7/vmxnet-only/vmxnet.c: In function ‘vmxnet_interrupt’:

/tmp/vmware-config7/vmxnet-only/vmxnet.c:2232: error: ‘struct net_device’ has no member named ‘priv’

/tmp/vmware-config7/vmxnet-only/vmxnet.c: In function ‘vmxnet_close’:

/tmp/vmware-config7/vmxnet-only/vmxnet.c:2314: error: ‘struct net_device’ has no member named ‘priv’

/tmp/vmware-config7/vmxnet-only/vmxnet.c: In function ‘vmxnet_load_multicast’:

/tmp/vmware-config7/vmxnet-only/vmxnet.c:2404: error: ‘struct net_device’ has no member named ‘priv’

/tmp/vmware-config7/vmxnet-only/vmxnet.c: In function ‘vmxnet_set_multicast_list’:

/tmp/vmware-config7/vmxnet-only/vmxnet.c:2465: error: ‘struct net_device’ has no member named ‘priv’

/tmp/vmware-config7/vmxnet-only/vmxnet.c: In function ‘vmxnet_get_stats’:

/tmp/vmware-config7/vmxnet-only/vmxnet.c:2545: error: ‘struct net_device’ has no member named ‘priv’

make[2]: *** Error 1

make[1]: *** Error 2

make[1]: Leaving directory `/usr/src/kernels/2.6.29.4-167.fc11.i686.PAE'

make: *** http://vmxnet.ko Error 2

make: Leaving directory `/tmp/vmware-config7/vmxnet-only'

Unable to build the vmxnet module.

-


Building the vmblock module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config8/vmblock-only'

make -C /lib/modules/2.6.29.4-167.fc11.i686.PAE/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.29.4-167.fc11.i686.PAE'

CC /tmp/vmware-config8/vmblock-only/linux/block.o

In file included from /tmp/vmware-config8/vmblock-only/linux/os.h:35,

from /tmp/vmware-config8/vmblock-only/linux/block.c:26:

/tmp/vmware-config8/vmblock-only/./include/compat_wait.h:78: error: conflicting types for ‘poll_initwait’

include/linux/poll.h:67: note: previous declaration of ‘poll_initwait’ was here

In file included from /tmp/vmware-config8/vmblock-only/linux/vmblockInt.h:40,

from /tmp/vmware-config8/vmblock-only/linux/block.c:29:

/tmp/vmware-config8/vmblock-only/./include/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined

make[2]: *** Error 1

make[1]: *** Error 2

make[1]: Leaving directory `/usr/src/kernels/2.6.29.4-167.fc11.i686.PAE'

make: *** http://vmblock.ko Error 2

make: Leaving directory `/tmp/vmware-config8/vmblock-only'

Unable to build the vmblock module.

-


Building the vmci module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config9/vmci-only'

make -C /lib/modules/2.6.29.4-167.fc11.i686.PAE/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.29.4-167.fc11.i686.PAE'

CC /tmp/vmware-config9/vmci-only/kernelStubsLinux.o

In file included from /tmp/vmware-config9/vmci-only/kernelStubs.h:35,

from /tmp/vmware-config9/vmci-only/kernelStubsLinux.c:28:

/tmp/vmware-config9/vmci-only/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined

CC /tmp/vmware-config9/vmci-only/vmciDatagram.o

In file included from /tmp/vmware-config9/vmci-only/vmciDatagram.c:42:

/tmp/vmware-config9/vmci-only/vm_basic_types.h:108:7: warning: "__FreeBSD__" is not defined

In file included from /tmp/vmware-config9/vmci-only/vmci_kernel_if.h:41,

from /tmp/vmware-config9/vmci-only/vmciDatagram.c:45:

/tmp/vmware-config9/vmci-only/compat_wait.h:78: error: conflicting types for ‘poll_initwait’

include/linux/poll.h:67: note: previous declaration of ‘poll_initwait’ was here

In file included from /tmp/vmware-config9/vmci-only/vmci_queue_pair.h:36,

from /tmp/vmware-config9/vmci-only/vmciGuestKernelAPI.h:43,

from /tmp/vmware-config9/vmci-only/vmciUtil.h:33,

from /tmp/vmware-config9/vmci-only/vmciDatagram.c:48:

/tmp/vmware-config9/vmci-only/vm_atomic.h:329:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:333:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:401:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:407:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:506:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:595:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:684:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:773:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:775:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:860:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:862:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:945:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:947:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:1028:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:1030:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:1223:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:1227:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:1536:7: warning: "_MSC_VER" is not defined

/tmp/vmware-config9/vmci-only/vm_atomic.h:1663:7: warning: "_MSC_VER" is not defined

make[2]: *** Error 1

make[1]: *** Error 2

make[1]: Leaving directory `/usr/src/kernels/2.6.29.4-167.fc11.i686.PAE'

make: *** http://vmci.ko Error 2

make: Leaving directory `/tmp/vmware-config9/vmci-only'

Unable to build the vmci module.

-


Reply
0 Kudos
14 Replies
NickP-CA
Contributor
Contributor

also seeing the same problem here.. .any response from VMW?

Reply
0 Kudos
bigfeetliu
Contributor
Contributor

!!!!!!!!!!!!!!!!!!!!!!!!

Reply
0 Kudos
vdanen
Contributor
Contributor

Just installed the GA of Fedora 11 here and I have the same compilation issues with vmware-tools. Does anyone have a solution for this yet?

Reply
0 Kudos
AntoineSolution
Contributor
Contributor

I am having the exact same issue, waiting for a solution from VMW!

Reply
0 Kudos
woodmeister
Enthusiast
Enthusiast

Please note that on the following link:

http://www.vmware.com/products/fusion/resources/system_requirements.html

Fedora is not officially supported by VMware Fusion.

However, several people on this forum have gotten other versions to work just fine.

(I currently have Fedora9 working with no issues.)

With that said, which OS option did you use when you first created the VM?

I use the "other linux" option. You may try that if you haven't already.

Reply
0 Kudos
bigfeetliu
Contributor
Contributor

I do not thik this is the cause.

I have successfully instralled fedora 10, with install option "redhat linux"。

The problem may be caused by kernel update in fedoar 11, which does not match vmware-config-tool rebuilding requirments!

Reply
0 Kudos
makowski_filip
Contributor
Contributor

I agree with that, Fedora 10 had no problem

byt the way, the open-vm package (Fusion repo) build ok under F11 (http://download1.rpmfusion.org/free/fedora/releases/11/Everything/x86_64/os/repoview/open-vm-tools.html)

but it lacks some feature (mouse related)

VMWare have to fixe their drivers, soon or later, the problem will raise on others distro, and that's not fair from VMWare

Reply
0 Kudos
cvidal09
Contributor
Contributor

Hi:

VMWare runs OK on FC11 if you apply the attached patch (done by Ehud, modified by Stericho, see http://communities.vmware.com/message/1141306#1141306).

The patch will fail for one of the sources, but it doesn't matter.

Reply
0 Kudos
makowski_filip
Contributor
Contributor

will try, but just to be sure, to which sources to you apply this patch ?

because it seems that they are different flavor and fusion is not workstation

Reply
0 Kudos
cvidal09
Contributor
Contributor

This is what you do as root (choose the work directory of your preference):

mkdir /home/vmwork

cd /home/vmwork

for i in /usr/lib/vmware/modules/source/*.tar ; do tar xvf $i; done

patch -p1 < the_patch_file.patch

find . -name \*.rej -exec rm -f {} \;

find -name \*.orig -exec rm -f {} \;

for d in *-only ; do tar cvf ${d%-only}.tar $d

cd /usr/lib/vmware/module/source

mkdir bak

mv *.tar bak

mv /home/vmwork/*.tar .

That's it!

Reply
0 Kudos
makowski_filip
Contributor
Contributor

no that's not it

the patch is made for which VMwareTools version ?

with the one we have under Fusion, this patch it not good

under Fusion we install VMwareTools-7.9.3-159196.tar.gz

it doesn't seems that you patch apply to this version

Reply
0 Kudos
cvidal09
Contributor
Contributor

You are right, the patch applies to VMWare, not VMWare-tools.

Reply
0 Kudos
SvenGus
Expert
Expert

FYI, the VMware Tools in version 2.0.5 (i.e., VMwareTools-7.9.6-173382) compile perfectly also in Fedora 11 (at least for the i386 DVD version with the i686 PAE kernel): so the problem should now be solved...

Reply
0 Kudos
AntoineSolution
Contributor
Contributor

I am using the latest version of VMware Workstatation. How do I get the latest VMware Tools for this?

Cheers,

Antoine

Reply
0 Kudos