As per this link:
I've followed the instructions in the link above, but during the installation of VMWare Tools (on the Ubuntu 8.10 Guest) I get stuck at the point here it says:
"None of the pre-built vmmemctl modules for VMware Tools is suitable for your running kernal. 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)?"
Now what do I do? I have no clue how to build a module, or even how / if a C compiler is installed, or how I would even install one. Could you please give us some step by step instructions on how to get VMWare Tools working on Ubuntu 8.10? (I'm using Ubuntu 8.10 Server). Thank-you!
I'm using VMWare Workstation 6.5 build 118166 as the Host (on Vista Ultimate x64), and using Ubuntu 8.10 Server (x86) as the Guest OS. I've found threads from October and November, complaining about VMWare Tools not working with Ubuntu 8.10, but still have found no solution. Could you please give us a step by step tutorial on how we can get the VMWare Tools working under Ubuntu 8.10?
Any ideas as to what I should do next? What is a "pre-built vmemctl module"? How do I fix this problem with VMWare Tools? How could I get VMWare Tools working under Ubuntu 8.10, any ideas?
Yeah, I've stumbled through several hundreds of posts over the past 10-12 hours, and I've visited about 40+ forums, and various websites. I've bounced between the Ubuntu and the VMWare forums, but the begging and pleading for help (from VMWare) to fix their broken product seems to fall upon deaf ears.
Haven't received a single response from ANY of the VMWare developers. Amazing at how poorly VMWare supports a COMMERCIAL product. I could understand if this was an "open source" free product, but as far as a commercial product is concerned, I'm pretty disappointed that "cries for help" have been going on for 3-4+ months now, and the issues seem to be completely ignored by VMWare and the VMWare developers.
I found this thread here:
I'm not sure if this helps you at all. But I think it has gotten me at least headed in the right direction. I've been unable to get an answer from any of the VMWare developers, and they seem to be "sleeping on the job" as far as support VMWare under Ubuntu 8.10.
I'll take a look at the link you sent, and if I can find a solution I'll post back my findings (and solution) if I can ever find one. Thanks for the response, and thanks for the help. Hopefully if enough of us work together, maybe we can fix VMWare's broken tools, and VMWare's broken product.
It seems odd that the "open source" community has to comb together to fix a broken commercial product. VMWare seems to continue to ignore the problems, and continue to stick their head in the sand. I'll comb over the link you sent from the Ubuntu forums, and hopefully we can get more help over at Ubuntu then we are getting from the VMWare developers.
I haven't found a single response from any of the VMWare developers as to how to resolve this issue, or get it fixed. I'll check the link you sent, because that's a new link that I haven't seen yet. I'll try it, and post back if I find a solution (or get it fixed, or get it to work).
Thanks for the response! It's pretty frustrating when VMWare doesn't work properly, just to say the least. Hopefully the Ubuntu developers can be a bit more help then the VMWare folks. VMWare seems to just ignore the cries and pleas for help from their PAYING CUSTOMERS, and leaves it up to the Open Source developers to fix all the bugs and problems with a commercial product like VMWare. Go figure.
Regardless, if I do find a fix, I'll post it back to this thread, just so others will have a solution (for Archive purposes).
Well not yet, but almost... I think I'm getting close...
I posted what I thought was the "fix", but i'm having a problem with one of the commands:
sudo for i in ; do sudo mv $ $-only; sudo tar -cf $.tar $-only; done
I've been unable to get that line to work. Any suggestions as to what could be wrong? Is that valid syntax? Is there an error with that line, or are there any other commands I could use to get those modules correctly moved into the VMware tools tarball?
Well almost done, but not quite finished yet...
I think I'm almost there. I'm having a problem tarring up the "vmblock, vmhgfs, vmmemctl, vmsync, and vmxnet modules" and putting those modules into the official VMWare Tools tarball. I posted what I thought was the solution on another thread, but I'm realizing that I'm having problems with this command:
*sudo for i in ; do sudo mv $ $-only; sudo tar -cf $.tar $-only; done
This falls under the section entitled:
"From the open source modules/linux folder we have the vmblock, vmhgfs, vmmemctl, vmsync and vmxnet modules that we need to tar up and place into the official VMware tools tarball:"
The second line down says:
*sudo for i in ; do sudo mv $ $-only; sudo tar -cf $.tar $-only; done
I've been unable to get that line to work. Any suggestions as to what could be wrong? Is there an error with that line, or are there any other commands I could use?
I see the files that need to be tarred up, but the command "sudo for i in *; do sudo mv $ blah blah blah" doesn't seem to work. It comes back with a bash: syntax error near unexpected token 'do'. Not sure what's wrong, how do I tar up those files and place them into the official VMware tools tarball, and when on earth is VMWare going to fix this, so that other users like me don't have to? Any help with the above command (tarring up the files and putting them into the VMware tools tarball, would be greatly appreciated. I awarded you "helpful" points so far, but once I can get this resolved, I'll gladly close this out as "solved/answered" and give you the full credit for "correct answer". As it's the closest solution I have found so far from anyone. I did notice that the other link you gave, actually was for 64-bit downloads, and I ammended the post that I had made with the links for i386 (32-bit) files. But I'm still stuck at the part with the "sudo for i in *; do sudo mv $ $-only; sudo tar, blah blah blah command. I appreciate the help, and I'm slowly getting there. I have a feeling that I'm getting close, I just need to figure out how to get those built modules into the VMWare Tools tarball, so I can go back and re-run the VMWare install.
Do you have any idea how I can get those modules placed inside the official VMWare Tools tarball? What commands would I type? For some reason it doesn't like the "do", and keeps coming back with a syntax error. Is there any way to break that command up into maybe 4 or 5 different commands (line by line) so that it's not one big command (separated by semi colons). This way I can see what is causing the error/problem. Is there another way to zip those files up and add them to the VMWare tools tarball?
This is what I've tried to do to overcome the problem I am having with that one line that seems to be causing errors for me.
So now I've gone to the "open-vm-tools/modules/linux" directory, and each directory inside of that folder, I'm renaming it to xxx-only (for example vmmemctl become vmmemctl-only)
There are the commands I have typed:
sudo mv vmmemctl vmmemctl-only
I repeated this for each and every directory under the "open-vm-tools/modules/linux" folder.
Next, I went back and tarred each directory as follows: "tar -cf xxx.tar xxx-only". (for example, tar -cf vmmemctl.tar vmmemctl-only).
Once each directory is tarred, then I copied the tars overwriting the existing Official VMWare Tools files.
The official tars are located in vmware-tools-distrib/lib/modules/source. So, for example, do a: "mv open-vm-tools/modules/linux/*.tar vmware-tools-distrib/lib/modules/source/", to move the new files and overwrite each one.
I followed a post from Mufassa located here:
Next just re-run vmware-config-tools.pl, accept all the standard default answers during installation and after the installation it will ask if you want to build each module. Just select yes. It will then build each module for your system. Select "no" when it asks about building the experimental module (after VMsync module is finished building). Poof - should all work. Test a shared folder appears under /mnt/hgfs/ to make sure things are working for you.
In essence, you end up using the open source versions of vmxnet, vmmemctl, vmhgfs and vmblock. This might be a useful fix in the future too - since vmware tools seem to break regularly when some new Ubuntu kernel comes out... the open source version seems to be updated more frequently. VMWare seems really really really slow in updating and rolling out the fixes for their VMWare Tools.
It works!!! I finally got everything working in Ubuntu 8.10!! After 12 1/2 hours, I found the solutions to everything and finally did get everything running under Ubuntu 8.10 guest OS. It took some work, but I finally got everything working. I can now cut & paste between host and guest and I can also do guest OS resizing, and everything finally works just fine! I finally figured everything out, and found the solutions to everything. Sweet!
Just post another quick post here (I gave you two partial credits already), but if you just post a quick reply and I'll just award you the full points for the correct answer since your post is the ONLY (and closest) response I have received so far, and thank-you so much for the help! The link you provided, along with a bit of hunting and poking, and then the post by Mufassa in another thread, combined with bits and pieces from another post I had found on a 3rd party website, was enough for me to piece together a solution for getting VMWare Tools to work under Ubuntu 8.10 guest OS. Just post a quick reply, and I'll award you the correct answer points, and then close this out as answered. Thanks.
I've posted ALL of my findings here on this page, and documented everything here. I'll save this as an "Archive" in case anyone else runs across this problem trying to get VMWare Tools installed under Ubuntu 8.10 Guest OS. So at least there is a solution for installing VMWare Tools under Ubuntu 8.10 posted with step by step instructions. The links provided, and text provided in this post, should be enough to easily get VMWare Tools installed properly under Ubuntu 8.10.
Thanks for that Ubuntu forums link! It helped quite a bit, and got me "over the hump". Now my next question is, how can I get VMWare Tools to load automatically when Ubuntu boots up? I was reading in a readme file that I found, that:
You can now run VMWare Tools by invoking the following command during an X server session:
I also read that:
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.
I also read:
To use vmxnet driver, restart networking using the following commands:
Also, if the virtual printer feature is enabled, you will need to restart the CUPS service to make use of this feature.
Now, one last question:
Do I have to manually start up and run VMWare Tools every time my Ubuntu machine starts up and everytime I login? Is there anyway I can add these commands to a startup script somehow so that VMWare Tools runs automatically anytime Ubuntu 8.10 boots up or somehow create a login script so when a user logs in to the machine VMWare Tools will automatically startup? Also is there any way to enable the advanced X features (guest resolution fit, drag & drop, and file and text copy/paste) by starting /usr/bin/vmware-user during a startup script or a login script? Do these commands need to be executing everytime the machine starts up or a user logins? Is there any way to create a script that will run VMWare Tools automatically by invoking the following command on startup "/usr/bin/vmware-toolbox"?
It would be really nice to have a VMWare Tools icon in GNOME (to show that VMWare Tools is running) in Ubuntu. Any ideas as to how I could do such a thing? I'd really like to have a small VMWare Tools icon (like in Windows) that shows in the status/task bar (near the date, and time) a small little VMWare Tools icon (to show that VMWare Tools is currently running).
Any ideas on how I could do this? I might need to write another tutorial (in a separate post) on how to create the login scripts to get the VMWare Tools to load automatically upon startup in Ubuntu 8.10. It sure would be nice to have a VMWare Tools icon in the toolbar/task menu, just showing that VMWare Tools is currently running on the guest machine.
I will like to add my voice to this ever increasing cries for help. I am having the sme problems that everyone is having. I am running Workstation 6.5 on a Vista 64-bit laptop host, and Fedora Core 9 guest. I have followed th instructionsin the VMware User's manual and other documentation (including many hours of googling for solution!) but like most I also get stuck at the point where it says:
"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)?"
Like one of the thread participant said, "Now what do I do? I have no clue how to build a module, or even how / if a C compiler is installed, or how I would even install one. Could you please give us some step by step instructions on how to get VMWare Tools working on Fedora 9?"
It seems that this has been a long overdue fix or at least a written stepwise solution is required here!! . VMware support, could you guys please give us a step by step tutorial on how we can get the VMWare Tools working under all the major Linux distribution? Isn't that part of the alure, seling point and promise to customers?
If anyone coms across a soution, could th please share it with here?
If you are running a 64-bit host operating system (Vista x64) then I suggest you read this guide here first, and follow the instructions:
That should get you up and running.
If you are running on a 32-bit host, then follow the instructions I have outlined above and throughout this thread. You need to download different files for 32-bit and 64-bit, but (guest OS). Not really sure about Fedora though, but it should be similar to Ubuntu (I would think). You may need to start a separate thread for Fedora help though. This is a guide for Ubuntu 8.10.
It would probably be best to start a separate thread for help with installing VMWare Tools under Fedora. You can try the instructions I've given for Ubuntu, but I'm not sure if they will or will not work under Fedora. Never tried it. You can give it a shot, and then let us know if it works, but it would really be best to just start a new thread for Fedora help.
Thanks for the help and the tips! It really got me going. I started a new thread for "Adding a VMWare Tools icon" to the taskbar. Still no clue how to do it yet, but I just started the new thread:
I also created a new tutorial on how to get VMWare network "bridging" to work under Ubuntu 8.10 (instead of using NAT).
That tutorial can be found here:
Instead of making a new forum post, I would suggest that someone do a "convert thread to document". this way you have something a bit more official, and it won't get rotated out. If the document works for a number of people, then I can make it into a KB for Workstation .... even if it's "unsupported" right now.