I'm trying to install VMWare Tools on Fedora (Linux) 14, 64 Bit Edition. I'm running VMWare Fusion for Mac 3.1.2 on Mac OS X Snow Leopard 10.6.6 for reference.
I switched to root, cd'd to my vmware-tools-distrb directory, and tried to run ./vmware-install.pl. Here's the error message I'm getting:
The command you're using doesn't make sense...
it should be:
./vmware-install.pl
not:
./vmware-install/pl
the / changes the path, so it's looking for something called 'pl' in a folder called 'vmware-install, when you really want to run the .pl script inside the current folder.
That being said, it might not (and probably won't) work because Fedora 14 is not a supported Guest OS (the kernel modules probably won't build).
Getting there! Now it's asking me this question:
What do I need to do to change the gcc path?
If you answer [yes] it should prompt you for the location of gcc.
If you don't have gcc installed, you'll need to install it first.
'which gcc' should tell you where it is if it is installed.
Here's what which gcc is giving me:
Seems I don't have it?
That looks to be correct.
You can try using Fedora's package manager to install it.
You'll probably need to install 'make', and also the kernel-headers.
But again, i'm going bet that even with the right build utilities, the kernel itself isn't supported so you'll get errors about the modules not compiling.
That's the challenge with cutting-edge distros like Fedora. The kernel tends to be newer than what we build with, which makes things 'not work'.
I'll give it a test right now to see if/how it breaks.
Okay, so i got it to work, with a little bit of wrestling.
Annoyingly, when I do 'yum install kernel-devel' and 'yum install kernel-headers', it gives me a version which isn't the currently running kernel.
So, i had to uname -a to get that, and then do 'yum install kernel-devel-2.6.35.6-45.fc14.i686' followed by 'yum install kernel-headers-2.6.35.6-45.fc14.i686
I hit a brick wall when the .pl script was trying to find the headers, even tho they were there.
Maybe you can get away with specifying the folder:
/usr/src/kernels/$(uname -r)*/include/linux/version.h
I just did this (as #su) BEFORE running the .pl script:
echo "#define UTS_RELEASE "$(uname -r)"" >> /usr/src/kernels/$(uname -r)*/include/linux/version.h
It found the headers after that and finished the installation.
I then rebooted, and now things work as expeted (tho I haven't done a lot of testing... just resizing the window, drag and drop and copy-paste from host-to-guest)
Let me know if that helps 😃
So do I need to first type in #su, then this?
echo "#define UTS_RELEASE "$(uname -r)"" >> /usr/src/kernels/$(uname -r)*/include/linux/version.h
Then run the install script? I think I get it, just making sure.
Sorry, let me clarify:
# indicates the Bash shell when logged in as the Root user, also known as the SuperUser when accessed from a different account.
You type 'su' (without the quotes), and that elevates you to root.
Then paste:
echo "#define UTS_RELEASE "$(uname -r)"" >> /usr/src/kernels/$(uname -r)*/include/linux/version.h
Then run the install script.
Hope that clarifies things 😃
Tried it, getting a couple errors.
Got this when I ran the command:
Okay...
Do this:
yum install gcc
Here's what I got so far. I am running a x64 (64 Bit) version of Fedora if that makes a difference:
Were you able to tell from my last post if the commands I tried worked correctly, or did they not work?
Thanks!
I finally ensured I got GCC installed, and the installation successfully went through! Some of the config process might not have went through since it was unable to find the proper kernel headers, but I was able to get enough of it installed and configured so that my display is clearer and those pesky "VmWare Tools are not installed" error messages are gone. Only a couple features may not work, but I can live with them, and if I can get the kernel headers to function better later on, re-run the config part of it and all will go well.
Thanks again!
Hey,
Sorry I haven't had a chance to respond, things have been busy for me at work lately. (we volunteer when we can here, but our day-to-day has to come first)
In my case, it found the headers I specified, and I didn't notice any loss of features (even Unity worked, to my surprise).
Fedora, however, is a 'bleeding edge' distro by design, so it's somewhat expected that you know a thing or two about how Linux works (and not just how to navigate a GUI and read instructions).
If you're looking to learn it more, than Fedora is a good choice.
If you want a stable desktop, I'd recommend using Ubuntu 10.10 or 10.04.
In a nutshell, 'that's linux for ya'. 😉
Glad I could point you in the right direction to help you figure it out 😃
Note: okay, unity just crashed the VM when going back to Single Window, but I sort of expect stuff to break because it's Fedora.
Thanks for all your help! Yeah, I've used Ubuntu in the past, and it's better for day-to-day use. The only reason I'm running Fedora is so I can compile our GEMPAK weather forecasting tool which runs on RPM Linux distros (I could choose either CentOS or Fedora, I chose Fedora since it seemed easier to install). Since that's all I'm doing with it, it should run OK for me, and VMWare Tools seems configed enough for what I need now. If I need a day-to-day Linux distro, I'd definitely use Ubuntu.
Ah, i see... Very Cool!
Thanks for sharing the use case!
Take Care 😃
Just followed your instructions and they worked perfectly. This was after piece mealing others together. Now even shared folders work.
Thanks!
Mickro,
I too just followed your instruction and it worked perfectly! I'm not sure what that echo statment did but I think it was key for this to work. I'm soo happy now that I don't have to boot into windows to work on my VM's. Your efforts are greatly appriciated !!