I did exactly what you did using the same distro and had the exact same error message.  Very interested in how to fix this...

The blog instructions worked fine to fix the hgfs problems.

However, I would suggest the following sequence:

a.  Run vmware-uninstall-tools.pl  (so you don't get that other message about the installed modules)

b. create the vmware-tools-distrib directory

c. Apply the fix as per the blog page

d. run  vmware-install.pl

If all else fails, follow the suggestion of the  error message to remove the modules "by hand" and then re-run the install

Could anyone of those who managed to fix the issue please give some more details where exaclty in file page.c they did the fixes? Was not clear to me reading the blog post.

Thanks,

vanduenkel

The blog uses a kind of shorthand (based on patch lines)

\- page = __grab_cache_page(mapping, index);

+ page = grab_cache_page_write_begin(mapping, index, flags);

it means:

find the line:

page = __grab_cache_page(mapping, index);

remove it and replace it with the following line:

page = grab_cache_page_write_begin(mapping, index, flags);

or you could read it as - make changes to the first line to make it look like the second line.

So, just search (in an editor) for  "__grab_cache_page"

You should then just be able to make the suggested change to the line.

vanduenkel wrote:

Could anyone of those who managed to fix the issue please give some more details where exaclty in file page.c they did the fixes? Was not clear to me reading the blog post.

I think the directions are self explanatory however maybe the following will make it clearer.

It is line 867 in the page.c file that is in the vmhgfs.tar tarball as shown in the attached image that needs to be patched.

I have also attached a page.c.patch.zip file that contains a diff patch created under Fusion 2.0.4 and have verified it will work with 2.0.2 and 2.03 and was not applicable to 2.0.1 or 2.0.0.  Note: The is for the page.c file that is in the vmhgfs.tar tarball in the VMwareTools.tar.gz file in the "/Library/Application Support/VMware Fusion/isoimages/linux.iso" file that is the VMware Tools for Linux when installing from the tar.gz installer.

The syntax to use the patch is: patch page.c page.c.patch

Message was edited by: WoodyZ - Updated the Fusion versions the page.c.patch file works with.

I think I made the page.c change and did the VMware Tools install/uninstall correctly, but I'm not seeing my shared folders. I've restarted and checked that shared folders are active in the VM settings. how do I fix this? where should the shared folders be showing up in Ubuntu?

ginswizzle wrote:

where should the shared folders be showing up in Ubuntu?

Look in: /mnt/hgfs

For those looking for an automated solution to installing VMware Tools in Ubuntu 9.04 Desktop Edition which incorporates information found in this thread and additional changes that need to be made have a look at: Installing Ubuntu 9.04 Desktop Edition with full support of VMware Tools - Simplified!

Woody, slightly off topic, but you may be able to help. I installed 8.0.4 JeOS which started life at about 100 megs. After install, it was about 455 megs. Then I did a minimal install of gnome-core synaptic, firefox and a few other things. This brought it up to 937 meg..Not so ideal, but I could live with that.

However, after doing build-essential and get the headers and stuff to load and install vmware-tools, I end up at 1.79 GB!  I was wondering if you can think of any way I can get back down to a lower number. I've tried the deborphan thing, the dead packages thing, etc. I just don't get why everything would bloat by 700 meg just because I took the steps to install vmware tools.

Can I get rid of all of the build tools? I don't think they took up that much. The vmware tar was 200 meg. That's gone. I just don't get what happened. This can't be all necessary code.

-Bob

The vmware tar was 200 meg. That's gone. I just don't get what happened. This can't be all necessary code.

A lot of the space taken up by Linux Tools is for prebuilt kernel modules, most of which you will probably never use. You can probably go through and prune them (though I forget where they end up), or even skip Tools installation entirely, which is what I do on my minimal installs.

Hi,

All I want is cut and paste between the XP host and the Ubuntu guest  and automatic resizing of the guest when the vm window is resized. Are you saying I can get away with no install or a smaller install of tools? If so, please give me a few tips on how to do that.

Also, how do you go about removing the unneeded stuff? What are the file suffixes?

I just also noticed a nasty bug with player: It always stays on top. I built the VM in workstation, so I hadn't seen the problem. I'm guessing the solution is to roll back to an earlier version of vmplayer. I have 2.5.2 right now.

This is the Fusion forum, so if you're using Player, that's important to know.

All I want is cut and paste between the XP host and the Ubuntu guest and automatic resizing of the guest when the vm window is resized.

Oh, I skimmed your post and based on the JeOS mention assumed that you had a minimal command-line installation (in which case you don't care about things like this because they won't work anyway).

Also, how do you go about removing the unneeded stuff?

Just sudo rm them, the tricky part is knowing which files you can get rid of safely. Like I said, I don't recall this off the top of my head.

Whoops! Sorry about being in the Fusion forum!  Yeah, I'm running vmware player on XP, though I got an invite in email to beta fusion so I'll be doing that soon.

I did find a HUGE file in my install which I deleted. I think when I did build-essential, the os made a backup copy of some core kernel file which was 400 meg. I deleted that on another build just to be sure nothing bad would happen, then deleted it on my normal system and all was well...until I used fslint to delete things.  Not a good idea. But I had a backup, so I was able to recover from that, too.

Biggest problem now: VMware Player 2.5.x has a bug relating to focus. If you click on another window, Player stays in the foreground unless you click on the title bar of the other  window. This is not good.