VMware Communities
RonaldVink
Contributor
Contributor

Fedora 11 and vmware tools

If you are using Fedora 11 with kernel 2.6.29.6-213.fc11.i686.PAE in workstation 6.5.2 , installation of vmware-tools will not work.

Put the partched tars in /usr/lib/vmware-tools/modules/source and rerun vmware-config-tools.pl.

Shared folders are working too.

Reply
0 Kudos
3 Replies
feffer777
Contributor
Contributor

Thx, that worked better. It looks like the vmmemctl and vmhgfs modules loaded, but vmxnet, vmblock and vmci still fail. Not sure what these affect. A snipped copy of the result follow. Ronald if you have any insight here, it would be greatly appreciated.

# /usr/bin/vmware-config-tools.pl

...

Building the vmmemctl module.

...

The vmmemctl module loads perfectly into the running kernel.

...

Building the vmhgfs module.

...

The vmhgfs module loads perfectly into the running kernel.

...

Building the vmxnet module.

Using 2.6.x kernel build system.

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

make -C /lib/modules/2.6.29.6-217.2.3.fc11.i586/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.29.6-217.2.3.fc11.i586'

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

/tmp/vmware-config18/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.6-217.2.3.fc11.i586'

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

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

Unable to build the vmxnet module.

The fast network device driver (vmxnet module) is used only for our fast

networking interface. The rest of the software provided by VMware Tools is

designed to work independently of this feature.

If you wish to have the fast network driver enabled, you can install the driver

by running vmware-config-tools.pl again after making sure that gcc, binutils,

make and the kernel sources for your running kernel are installed on your

machine. These packages are available on your distribution's installation CD.

None of the pre-built vmblock modules for VMware Tools is suitable for your

running kernel. Do you want this program to try to build the vmblock module

for your system (you need to have a C compiler installed on your system)?

Extracting the sources of the vmblock module.

Building the vmblock module.

Using 2.6.x kernel build system.

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

make -C /lib/modules/2.6.29.6-217.2.3.fc11.i586/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.29.6-217.2.3.fc11.i586'

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

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

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

/tmp/vmware-config19/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-config19/vmblock-only/linux/vmblockInt.h:40,

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

/tmp/vmware-config19/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.6-217.2.3.fc11.i586'

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

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

Unable to build the vmblock module.

The vmblock module enables dragging or copying files from within a host and

dropping or pasting them onto your guest (host to guest drag and drop and file

copy/paste). The rest of the software provided by VMware Tools is designed to

work independently of this feature (including guest to host drag and drop and

file copy/paste).

If you would like the host to guest drag and drop and file copy/paste features,

you can install the driver by running vmware-config-tools.pl again after making

sure that gcc, binutils, make and the kernel sources for your running kernel

are installed on your machine. These packages are available on your

distribution's installation CD.

The VMware FileSystem Sync Driver (vmsync) is a new feature that

creates backups of virtual machines. Please refer to the VMware Knowledge Base

for more details on this capability. Do you wish to enable this feature?

None of the pre-built vmci modules for VMware Tools is suitable for your

running kernel. Do you want this program to try to build the vmci module for

your system (you need to have a C compiler installed on your system)?

Extracting the sources of the vmci module.

Building the vmci module.

Using 2.6.x kernel build system.

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

make -C /lib/modules/2.6.29.6-217.2.3.fc11.i586/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.29.6-217.2.3.fc11.i586'

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

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

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

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

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

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

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

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

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

/tmp/vmware-config20/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-config20/vmci-only/vmci_queue_pair.h:36,

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

/tmp/vmware-config20/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.6-217.2.3.fc11.i586'

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

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

Unable to build the vmci module.

The communication service is used in addition to the standard communication

between the guest and the host. The rest of the software provided by VMware

Tools is designed to work independently of this feature.

If you wish to have the VMCI feature, you can install the driver by running

vmware-config-tools.pl again after making sure that gcc, binutils, make and the

kernel sources for your running kernel are installed on your machine. These

packages are available on your distribution's installation CD.

Checking acpi hot plug

Starting VMware Tools services in the virtual machine:

Switching to guest configuration:

Guest filesystem driver:

Mounting HGFS shares:

Guest memory manager:

Guest operating system daemon:

Virtual Printing daemon:

The configuration of VMware Tools 6.5.0 build-118166 for Linux for this running

kernel completed successfully.

You must restart your X session before any mouse or graphics changes take

effect.

You can now run VMware Tools by invoking the following command:

"/usr/bin/vmware-toolbox" during an X server session.

To enable advanced X features (e.g., guest resolution fit, drag and drop, and

file and text copy/paste), you will need to do one (or more) of the following:

1. Manually start /usr/bin/vmware-user

2. Log out and log back into your desktop session; and,

3. Restart your X session.

If the virtual printer feature is enabled, you will need to restart the CUPS

service to make use of this feature.

Enjoy,

--the VMware team

Reply
0 Kudos
cms33
Contributor
Contributor

Have these other vmware-tool issues been resolved? Is there a patch?

Reply
0 Kudos
jwnchoate
Contributor
Contributor

same problem as posted above, kernel is now 2.6.30.8-64.cf11.x86_64

Reply
0 Kudos