VMware Communities
mickeyfmann
Contributor
Contributor
‎05-31-2008 07:26 AM

Problems with Installing VMware Workstation 6.0 on Fedora 9 core

I'm trying to install Vmware Workstation 6.0 on the newly released Fedora 9 Core and I keep running into issues.

This is the output

# vmware-config.pl

Making sure services for VMware Workstation are stopped.

Stopping VMware services:

Virtual machine monitor

Configuring fallback GTK+ 2.4 libraries.

In which directory do you want to install the theme icons?

What directory contains your desktop menu entry files? These files have a

.desktop file extension.

In which directory do you want to install the application's icon?

/usr/share/applications/vmware-workstation.desktop: warning: value "vmware-workstation.png" for key "Icon" in group "Desktop Entry" is an icon name with an extension, but there should be no extension as described in the Icon Theme Specification if the value is not an absolute path

/usr/share/applications/vmware-player.desktop: warning: value "vmware-player.png" for key "Icon" in group "Desktop Entry" is an icon name with an extension, but there should be no extension as described in the Icon Theme Specification if the value is not an absolute path

Trying to find a suitable vmmon module for your running kernel.

None of the pre-built vmmon modules for VMware Workstation is suitable for your

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

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

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

What is the location of the directory of C header files that match your running

kernel?

Extracting the sources of the vmmon module.

Building the vmmon module.

Building for VMware Workstation 6.0.0.

Using 2.6.x kernel build system.

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

make -C /lib/modules/2.6.25.3-18.fc9.i686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.25.3-18.fc9.i686'

CC /tmp/vmware-config7/vmmon-only/linux/driver.o

CC /tmp/vmware-config7/vmmon-only/linux/driverLog.o

CC /tmp/vmware-config7/vmmon-only/linux/hostif.o

CC /tmp/vmware-config7/vmmon-only/common/comport.o

CC /tmp/vmware-config7/vmmon-only/common/cpuid.o

In file included from /tmp/vmware-config7/vmmon-only/./include/vcpuset.h:74,

from /tmp/vmware-config7/vmmon-only/./include/modulecall.h:23,

from /tmp/vmware-config7/vmmon-only/common/vmx86.h:19,

from /tmp/vmware-config7/vmmon-only/common/hostif.h:18,

from /tmp/vmware-config7/vmmon-only/common/cpuid.c:15:

include/asm/bitops.h:9:2: error: #error only can be included directly

In file included from include/asm/cpufeature.h:118,

from include/asm/alternative.h:42,

from include/asm/bitops.h:13,

from /tmp/vmware-config7/vmmon-only/./include/vcpuset.h:74,

from /tmp/vmware-config7/vmmon-only/./include/modulecall.h:23,

from /tmp/vmware-config7/vmmon-only/common/vmx86.h:19,

from /tmp/vmware-config7/vmmon-only/common/hostif.h:18,

from /tmp/vmware-config7/vmmon-only/common/cpuid.c:15:

include/linux/bitops.h: In function ‘get_bitmask_order':

include/linux/bitops.h:29: error: implicit declaration of function ‘fls'

include/linux/bitops.h: In function ‘hweight_long':

include/linux/bitops.h:45: error: implicit declaration of function ‘hweight32'

include/linux/bitops.h:45: error: implicit declaration of function ‘hweight64'

include/linux/bitops.h: In function ‘fls_long':

include/linux/bitops.h:112: error: implicit declaration of function ‘fls64'

In file included from include/asm/bitops.h:316,

from /tmp/vmware-config7/vmmon-only/./include/vcpuset.h:74,

from /tmp/vmware-config7/vmmon-only/./include/modulecall.h:23,

from /tmp/vmware-config7/vmmon-only/common/vmx86.h:19,

from /tmp/vmware-config7/vmmon-only/common/hostif.h:18,

from /tmp/vmware-config7/vmmon-only/common/cpuid.c:15:

include/asm/bitops_32.h: At top level:

include/asm/bitops_32.h:134: error: static declaration of ‘fls' follows non-static declaration

include/linux/bitops.h:29: error: previous implicit declaration of ‘fls' was here

In file included from include/asm/bitops_32.h:145,

from include/asm/bitops.h:316,

from /tmp/vmware-config7/vmmon-only/./include/vcpuset.h:74,

from /tmp/vmware-config7/vmmon-only/./include/modulecall.h:23,

from /tmp/vmware-config7/vmmon-only/common/vmx86.h:19,

from /tmp/vmware-config7/vmmon-only/common/hostif.h:18,

from /tmp/vmware-config7/vmmon-only/common/cpuid.c:15:

include/asm-generic/bitops/hweight.h:6: error: conflicting types for ‘hweight32'

include/linux/bitops.h:45: error: previous implicit declaration of ‘hweight32' was here

include/asm-generic/bitops/hweight.h:9: error: conflicting types for ‘hweight64'

include/linux/bitops.h:45: error: previous implicit declaration of ‘hweight64' was here

In file included from include/asm/bitops_32.h:149,

from include/asm/bitops.h:316,

from /tmp/vmware-config7/vmmon-only/./include/vcpuset.h:74,

from /tmp/vmware-config7/vmmon-only/./include/modulecall.h:23,

from /tmp/vmware-config7/vmmon-only/common/vmx86.h:19,

from /tmp/vmware-config7/vmmon-only/common/hostif.h:18,

from /tmp/vmware-config7/vmmon-only/common/cpuid.c:15:

include/asm-generic/bitops/fls64.h:6: error: static declaration of ‘fls64' follows non-static declaration

include/linux/bitops.h:112: error: previous implicit declaration of ‘fls64' was here

make[2]: *** Error 1

make[1]: *** Error 2

make[1]: Leaving directory `/usr/src/kernels/2.6.25.3-18.fc9.i686'

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

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

Unable to build the vmmon module.

For more information on how to troubleshoot module-related problems, please

visit our Web site at "http://www.vmware.com/download/modules/modules.html" and

"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".

Execution aborted.

I've tried running the any-any patch but didn't get much of a difference in the results. I've looked around for any other articles about this topic but didn't find much which is probably due to the relatively young age of Fedora 9, anyways any help anyone could provide here would be awesome because I'd really like to keep Fedora 9 on this machine.

Thanks

Reply
0 Kudos
3 Replies
mickeyfmann
Contributor
Contributor
‎05-31-2008 10:10 AM

After a bit of googling and a lot of fun I was able to get this to work, see the link below if you happen to have this same issue, the guide I found works very well.

Reply
0 Kudos
clive_long
Contributor
Contributor
‎07-01-2008 02:55 AM

Hi,

I am also experiencing problems configuring VM WS 6.0.x on Fedora9 (details below). VM WS configures fine with Fedora7 2.6.23 kernel.

I will follow the link and post the results

Why is this always such a trial when the kernel is upgraded?

Clive

# cd /usr/bin

# uname -a

Linux Linux26G 2.6.25-14.fc9.i686 #1 SMP Thu May 1 06:28:41 EDT 2008 i686 i686 i386 GNU/Linux

# ./vmware-config.pl

Making sure services for VMware Workstation are stopped.

Stopping VMware services:

Virtual machine monitor

Blocking file system:

Bridged networking on /dev/vmnet0

Host network detection

Bridged networking on /dev/vmnet1

Virtual ethernet

Configuring fallback GTK+ 2.4 libraries.

In which directory do you want to install the theme icons?

What directory contains your desktop menu entry files? These files have a

.desktop file extension.

In which directory do you want to install the application's icon?

Trying to find a suitable vmmon module for your running kernel.

None of the pre-built vmmon modules for VMware Workstation is suitable for your

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

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

Using compiler "/usr/bin/gcc". Use environment variable CC to override.

What is the location of the directory of C header files that match your running

kernel?

Extracting the sources of the vmmon module.

Building the vmmon module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config10/vmmon-only'

make -C /lib/modules/2.6.25-14.fc9.i686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.25-14.fc9.i686'

CC /tmp/vmware-config10/vmmon-only/linux/driver.o

CC /tmp/vmware-config10/vmmon-only/linux/hostif.o

CC /tmp/vmware-config10/vmmon-only/common/comport.o

CC /tmp/vmware-config10/vmmon-only/common/cpuid.o

CC /tmp/vmware-config10/vmmon-only/common/hash.o

CC /tmp/vmware-config10/vmmon-only/common/memtrack.o

CC /tmp/vmware-config10/vmmon-only/common/phystrack.o

CC /tmp/vmware-config10/vmmon-only/common/task.o

CC /tmp/vmware-config10/vmmon-only/common/vmciContext.o

CC /tmp/vmware-config10/vmmon-only/common/vmciDatagram.o

CC /tmp/vmware-config10/vmmon-only/common/vmciDriver.o

CC /tmp/vmware-config10/vmmon-only/common/vmciDs.o

CC /tmp/vmware-config10/vmmon-only/common/vmciGroup.o

CC /tmp/vmware-config10/vmmon-only/common/vmciHashtable.o

CC /tmp/vmware-config10/vmmon-only/common/vmciProcess.o

CC /tmp/vmware-config10/vmmon-only/common/vmciResource.o

CC /tmp/vmware-config10/vmmon-only/common/vmciSharedMem.o

CC /tmp/vmware-config10/vmmon-only/common/vmx86.o

CC /tmp/vmware-config10/vmmon-only/vmcore/moduleloop.o

LD /tmp/vmware-config10/vmmon-only/vmmon.o

Building modules, stage 2.

MODPOST 1 modules

WARNING: modpost: module vmmon.ko uses symbol 'init_mm' marked UNUSED

CC /tmp/vmware-config10/vmmon-only/vmmon.mod.o

LD /tmp/vmware-config10/vmmon-only/vmmon.ko

make[1]: Leaving directory `/usr/src/kernels/2.6.25-14.fc9.i686'

cp -f vmmon.ko ./../vmmon.o

make: Leaving directory `/tmp/vmware-config10/vmmon-only'

The module loads perfectly in the running kernel.

/dev is dynamic:

Trying to find a suitable vmblock module for your running kernel.

None of the pre-built vmblock modules for VMware Workstation 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-config10/vmblock-only'

make -C /lib/modules/2.6.25-14.fc9.i686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.25-14.fc9.i686'

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

CC /tmp/vmware-config10/vmblock-only/linux/control.o

CC /tmp/vmware-config10/vmblock-only/linux/dbllnklst.o

CC /tmp/vmware-config10/vmblock-only/linux/dentry.o

/tmp/vmware-config10/vmblock-only/linux/dentry.c: In function ‘DentryOpRevalidate':

/tmp/vmware-config10/vmblock-only/linux/dentry.c:101: error: ‘struct nameidata' has no member named ‘dentry'

/tmp/vmware-config10/vmblock-only/linux/dentry.c:101: error: ‘struct nameidata' has no member named ‘dentry'

/tmp/vmware-config10/vmblock-only/linux/dentry.c:102: error: implicit declaration of function ‘path_release'

make[2]: *** Error 1

make[1]: *** Error 2

make[1]: Leaving directory `/usr/src/kernels/2.6.25-14.fc9.i686'

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

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

Unable to build the vmblock module.

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

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

copy/paste). The rest of the software provided by VMware Workstation is

designed to work independently of this feature (including host to guest drag

and drop and file copy/paste).

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

you can install the driver by running vmware-config.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.

/dev is dynamic:

This program previously created the file /dev/vmnet0, and was about to remove

it. Somebody else apparently did it already.

This program previously created the file /dev/vmnet1, and was about to remove

it. Somebody else apparently did it already.

You have already setup networking.

Would you like to skip networking setup and keep your old settings as they are?

(yes/no)

Trying to find a suitable vmnet module for your running kernel.

None of the pre-built vmnet modules for VMware Workstation is suitable for your

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

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

Extracting the sources of the vmnet module.

Building the vmnet module.

Using 2.6.x kernel build system.

make: Entering directory `/tmp/vmware-config11/vmnet-only'

make -C /lib/modules/2.6.25-14.fc9.i686/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.25-14.fc9.i686'

CC /tmp/vmware-config11/vmnet-only/driver.o

In file included from /tmp/vmware-config11/vmnet-only/vnet.h:13,

from /tmp/vmware-config11/vmnet-only/vnetInt.h:10,

from /tmp/vmware-config11/vmnet-only/driver.c:40:

/tmp/vmware-config11/vmnet-only/vm_basic_types.h:170: error: conflicting types for ‘uintptr_t'

include/linux/types.h:40: error: previous declaration of ‘uintptr_t' was here

In file included from /tmp/vmware-config11/vmnet-only/vm_basic_asm.h:28,

from /tmp/vmware-config11/vmnet-only/vm_oui.h:14,

from /tmp/vmware-config11/vmnet-only/vnetInt.h:11,

from /tmp/vmware-config11/vmnet-only/driver.c:40:

/tmp/vmware-config11/vmnet-only/x86cpuid.h:383:1: warning: "BIT_MASK" redefined

In file included from include/linux/kernel.h:15,

from /tmp/vmware-config11/vmnet-only/driver.c:9:

include/linux/bitops.h:7:1: warning: this is the location of the previous definition

make[2]: *** Error 1

make[1]: *** Error 2

make[1]: Leaving directory `/usr/src/kernels/2.6.25-14.fc9.i686'

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

make: Leaving directory `/tmp/vmware-config11/vmnet-only'

Unable to build the vmnet module.

For more information on how to troubleshoot module-related problems, please

visit our Web site at "http://www.vmware.com/download/modules/modules.html" and

"http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html".

Execution aborted.

#

Reply
0 Kudos
SVRCFL
Contributor
Contributor
‎07-08-2008 09:33 PM

You should be able to compile all required modules just by patching vmblock alone (and not vmnet or vmmon). This appears to have worked for the last several kernels (last tested on 2.6.25.9-76), using the vmblock.patch file from above.

Reply
0 Kudos