VMware Cloud Community
pmatthaei
Contributor
Contributor

VMWare Tools won't install on Fedora 12, because of gcc 4.4.2

Hello,

we are using ESXi 4 and VMWare Tools 4.0.0-20816, no we have got a Fedora 12 machine, where GCC 4.4.2 and Kernel 2.6.31.9-174.fc12.i686.PAE is on board.

The tools won't compile the kernel modules, so on the machine is horrible slow..

I get this:

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

running kernel. Do you want this program to try to build the vmhgfs 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.

Your compiler "/usr/bin/gcc" version "gcc-Version 4.4.2 20091222 (Red Hat

4.4.2-20) (GCC) " is not supported by this version of VMware Tools.

The filesystem driver (vmhgfs module) is used only for the shared folder

feature. The rest of the software provided by VMware Tools is designed to work

independently of this feature.

Does anyone have got a patch to make it work?

Thanks.

Message was edited by: pmatthaei

Reply
0 Kudos
13 Replies
phaze75
Contributor
Contributor

Hi,

same problem here.

*) Host System: VMware

Server Version

2.0.1 Build 156745 running on Windows 2003 Server R2, 64 Bit

*) Guest System: Fedora Core 12, kernel: 2.6.32.11-99.fc12.i686.PAE

vmware-config-tools simply won't compile without errors. I read a lot of postings around the 'net, still no solution yet.

Am i wrong, or is there a solutionout there that solves this problem? ?:|

Cheers!

Reply
0 Kudos
golddiggie
Champion
Champion

Use yum to install all the kernel devel items into the guest...

VMware VCP4

Consider awarding points for "helpful" and/or "correct" answers.

Reply
0 Kudos
pmatthaei
Contributor
Contributor

Hello,

there is only the x11 driver available:

  1. yum search vmware

Geladene Plugins: refresh-packagekit

================================================================== Matched: vmware ===================================================================

xorg-x11-drv-vmware.i686 : Xorg X11 vmware Video-Treiber

I have also searched for vcp and didn't found anything.

Reply
0 Kudos
golddiggie
Champion
Champion

try

yum install kernel*

Did you customize the installation, or just take the defaults?

-update-

I installed using the customize function and made sure to add the GCC items, as well as the development libraries and such (including the additional items to make sure nothing was missed). Using the yum install kernel* command (you'll need to su - first) I was able to then install the VMware Tools on a Fedora 12 (32 bit) VM on my ESXi 4 u1 (same as you) host. The tools install does have to compile for the kernel since it's not in the existing tools install. I'm sure given enough time, and updates, you won't have to let it recompile, but by then, Fedora 13 will probably be out.

Personally, I prefer to use RHEL or CentOS for Linux as guest servers/systems under ESX/ESXi... If anything, I would put Fedora 12 under VMware Workstation 7.1, since support for it is listed in the items for "what's new"...

VMware VCP4

Consider awarding points for "helpful" and/or "correct" answers.

Reply
0 Kudos
pmatthaei
Contributor
Contributor

It isn't customized, it is just a Fedora 12 i386 with a PAE Kernel. The kernel and devel packages are surely already installed, I am running now 2.6.32.11-99.fc12.i686.PAE

However:

# modinfo vmxnet

ERROR: modinfo: could not find module vmxnet

# modinfo vmmemctl

ERROR: modinfo: could not find module vmmemctl

#

And vmware tool installer 4.0.0-236512 still says:

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

Your compiler "/usr/bin/gcc" version "gcc-Version 4.4.3 20100127 (Red Hat

4.4.3-4) (GCC) " is not supported by this version of VMware Tools.

Reply
0 Kudos
golddiggie
Champion
Champion

If you just took all the defaults for what was installed when you built the VM, then I would say that's at least part of your issue. As a matter of habbit, any time I install a Linux OS I customize the installation to ensure what I'll want to run is on there from the start. Far easier to do it at install time than try to figure it out later. If it's going to be a VM, I always include the Development Libraries as well as the Development items such as gcc.

Right after I installed Fedora 12 (yesterday) I ran a full update session (using yum extender). It found a TON of items to update. I had used the "yum install kernel*" command first, to ensure all the items needed for the VMware Tools were installed. Wouldn't you know it, VMware Tools installed without any errors, just telling me it was recompiling using the items present on the VM since it didn't have a pre-compiled set already. Just meant more taps of the "enter" key for me... No big deal.

Double check to make sure you have ALL the kernel items needed for the VMware Tools to install. It sounds like you either skipped, or missed something during your install. I would also use the yum extender to make sure you're fully up to date as well. It really sounds like you're missing something in the build.

You could always try a fresh VM, customizing it during the install process to include the development items/categories and try again. That is, if you want to have the tools installed and not just grumble about it.

VMware VCP4

Consider awarding points for "helpful" and/or "correct" answers.

Reply
0 Kudos
pmatthaei
Contributor
Contributor

1) The installation is up to date

2) Every compiler (g++, cpp, gcc) the libc development versions etc are installed, I am also able to compile other kernel modules

3) and for your kernel line, there is also everything installed:

kernel-PAE-devel-2.6.32.10-90.fc12.i686

kernel-PAE-2.6.31.12-174.2.3.fc12.i686

kernel-firmware-2.6.32.11-99.fc12.noarch

kernel-PAE-devel-2.6.32.11-99.fc12.i686

kernel-PAE-devel-2.6.31.12-174.2.3.fc12.i686

kernel-PAE-2.6.32.10-90.fc12.i686

kernel-headers-2.6.32.11-99.fc12.i686

kernel-PAE-2.6.32.11-99.fc12.i686

I don't know how this is related to the message "we do not support this gcc version and doing nothing now".

I am not a fedora export, we just have got one of this server but a ton of debian servers and there I am an expert, sorry but this is no PICNIC-problem as in "I don't know what I am doing and executing random commands would lead me to my goal"..

Reply
0 Kudos
pmatthaei
Contributor
Contributor

So I have solved the problem now and yes it wasn't a fault of my...

I have wrote the attached patch for the vmware tools which solves all problems

Message was edited by: pmatthaei

Reply
0 Kudos
phaze75
Contributor
Contributor

Well, this won't solve my problem, as my gcc is accepted by VMware Tools. It just doesn't compile correctly:

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

running kernel. Do you want this program to try to build the vmmemctl 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 vmmemctl module.

Building the vmmemctl module.

Using 2.6.x kernel build system.

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

make -C /lib/modules/2.6.32.11-99.fc12.i686.PAE/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules

make[1]: Entering directory `/usr/src/kernels/2.6.32.11-99.fc12.i686.PAE'

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

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

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

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

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

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

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

include/linux/poll.h:70: 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.32.11-99.fc12.i686.PAE'

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

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

Unable to build the vmmemctl module.

Reply
0 Kudos
golddiggie
Champion
Champion

Here's a thought...

If you really do need to run Fedora 12 in a VM, use VMware Workstation 7.1, where it's fully supported. Then run Fedora 11 under ESX/ESXi where the tools will install without any complaints.

VMware VCP4

Consider awarding points for "helpful" and/or "correct" answers.

Reply
0 Kudos
pmatthaei
Contributor
Contributor

Still buggy in the U2 release, and this is such a simple patch..

Reply
0 Kudos
DSTAVERT
Immortal
Immortal

You might want to consider the OSP http://www.vmware.com/download/packages.html Add the repository to FC and update with YUM

-- David -- VMware Communities Moderator
pmatthaei
Contributor
Contributor

Cute, it still has not been fixed with the current vmware tools Smiley Sad

Reply
0 Kudos