This HowTo contains information for installing the VMWare Tools on Ubuntu 8.10 Intrepid. I include information for installing on a server instance or a desktop instance, which have different requirements. The desktop instance is more involved due to the additional requirements for X. If you are installing on a server instance, I tell you when to skip steps.

I update this page as new versions are released. You can see the revision history at the bottom.

Scripts

I developed a couple of automated scripts that perform these steps. If you wish to walk through the steps manually, skip to the next section. Otherwise, you can get the scripts at gitHub: server script, desktop script.

Getting Started

Note: due to the link to the kernel headers in the tools, you will need to reconfigure the VMWare tools each time the kernel is updated.

Prep

For purposes of this HowTo, I will assume use of a work directory named vmwaretools in your user home directory. If you want to follow these steps exactly, you can create and get to that directory now:

mkdir ~/vmwaretools
cd ~/vmwaretools

If you prefer to use your own location, replace ~/vmwaretools in the instructions below accordingly, but switch to the directory now.

Obtain external Library sources

Installation of the VMWare Tools on Ubuntu 8.10 requires you compile the Open VM Tools. You need to download the latest version of the Open VM Tools from Source Forge. I developed these steps using the 2009.03.18-154848 version (link):

wget -c http://internap.dl.sourceforge.net/sourceforge/open-vm-tools/open-vm-tools-2009.03.18-154848.tar.gz

Extract the contents of the Open VM Tools tar ball to our work directory:

tar xvfz open-vm-tools-*.tar.gz

“Install” the VMWare Tools from your VMWare Console by selecting the VM -> Install VMWare Tools… menu option. In the desktop version, this will mount the CD image with the VMWare Tools from your VMWare installation. In the server version, you will likely need to mount the image:

sudo mount -t iso9660 /dev/scd0 /media/cdrom0

Extract the contents of the VMWare Tools tar ball to our work directory:

tar xvfz /media/cdrom/VMwareTools-*.tar.gz

Add Build Packages from Ubuntu repositories

We will be compiling software requiring a build environment and a few libraries available directly from the Ubuntu repositories. Install these now:

sudo apt-get install build-essential libproc-dev \
libicu-dev libdumbnet-dev libglib2.0-dev libnotify-dev \
libfuse-dev linux-headers-`uname -r`

If you are installing the tools on a server instance, you are done with prep and can jump to the “Compile and Install Tools” section.

Additional Getting Started Steps for Desktop Install

When installing the tools on a desktop instance, we need to compile an updated version of one library and install a few more libraries from the Ubuntu repositories.

Obtain additional external Library sources

Unfortunately, the liburiparser package in the Ubuntu repository is not new enough for the open vm tools. We need to obtain and compile latest version of this library (link):

wget -c http://internap.dl.sourceforge.net/sourceforge/uriparser/uriparser-0.7.3.tar.gz

Extract the contents and get into the new directory:

tar xvfz uriparser-*.tar.gz
cd uriparser-*

Compile, make and install the library:

./configure && make
sudo make install

In order for the open vm tools compile step to find the new library, you will need to set a couple of environment variables. At the command prompt, enter the following:

export CFLAGS="-I /usr/local/include/uriparser"
export CPPFLAGS="-I /usr/local/include/uriparser"
cd .. # to get back to the work directory

Note: you can skip the export statements above if the library is installed in a standard location. I just preferred to do it this way. Check out the configure options using ./configure –help to determine what to set.

Add Additional Build Packages from Ubuntu repositories

We also need a few more libraries for the desktop install to address the X dependencies. Pull those now:

sudo apt-get install libgtk2.0-dev libgtkmm-2.4-dev xorg-dev

The actual list of packages is quite a bit more than our previous pull from the repository, so this will take a few minutes.

Compile and Install the Tools

Time to compile. From the work directory, switch to the open vm tools source directory we extracted above, configure and make:

cd open-vm-tools-*

If installing on a server instance, configure this way:

./configure --without-x

If installing on a desktop instance, configure this way:

./configure

Now you can compile:

make

Once compilation completes (make sure there are no errors after configure or make), we need to bundle the compilation output and overlay the versions provided by VMWare. Again from the work directory:

cd modules/linux

for i in *; \
do mv ${i} ${i}-only; \
tar -cf ${i}.tar ${i}-only; \
done

cd ../../..

mv -f open-vm-tools-*/modules/linux/*.tar \
vmware-tools-distrib/lib/modules/source/

Now that we replaced the VMWare provided tools with our freshly compiled versions, we can install the tools:

cd vmware-tools-distrib/
sudo ./vmware-install.pl

As you go through the install, answer the questions according to your preferences. The default answers work for the majority, including me.

Done

Reboot.

Thanks for reading. Leave me comments if this was useful or not.

Revisions:

Update 2/19/2009: Updated with latest release of open-vm-tools and new glib >= 2.6 dependency.

Update 2/23/2009: Noticed some warnings in the build of the desktop tools due to missing libnotify-dev and libfuse-dev.

Note 2/23/2009: I posted a script for the server edition of the tools on 2/3. I posted a script I put together today for the desktop steps.

Update 3/28/2009: Updated with latest release of open-vm-tools (2009-03-18).   Different packages included for the server install that hopefully helps people get hgfs working.

38 Comments

    • jing
    • Posted December 18, 2008 at 12:44 am
    • Permalink

    if you’re new to linux one cannot tell where a command begins and where it starts.

    • jing
    • Posted December 18, 2008 at 12:51 am
    • Permalink

    okay…. where is this suppose to go????

    for i in *; \
    do mv ${i} ${i}-only; \
    tar -cf ${i}.tar ${i}-only; \
    done

    • cccarey
    • Posted December 18, 2008 at 6:46 am
    • Permalink

    Paste or type it in the command line verbatim once you are in the ~/vmwaretools/open-vm-tools*/modules/linux folder. The command basically renames each file in the directory by appending “-only” to it, then puts it in a tar ball. The vmware-install step needs it in this format when it installs the tools.

    • luigi65
    • Posted December 23, 2008 at 8:47 am
    • Permalink

    Perfect! Works very fine. Thanks

    • Matt
    • Posted December 27, 2008 at 8:56 am
    • Permalink

    Thanks for the info!

    Couple of problems with your for loop in my case.
    In modules/linux I actually had some .o files as well as the directories so things got messy, also, the script can only ever be run once because you mv the original, I’d rather leave it in tact. So I made the following mods so it only tars the dirs, removes the old -only and copies the dir recursively instead of moving:

    #!/bin/bash
    for i in *; do
    if [ -d ${i} ]; then
    rm -rf ${i}-only
    cp -R ${i} ${i}-only
    tar cf ${i}.tar ${i}-only
    fi
    done

    • Erich Neuwirth
    • Posted January 14, 2009 at 6:23 am
    • Permalink

    I followed the instructions and could install the modified tools.
    Drag and drop between host and guest still does not work,
    and when I activate Shared folders and then try to access a host folder in /mnt/hgfs the system hangs and I need to reset it.

    • Erich Neuwirth
    • Posted January 14, 2009 at 6:27 am
    • Permalink

    Correction: Shared folders did not work with My Documents, but it works with other directories.
    Drag and drop still does not work.

    • cccarey
    • Posted January 14, 2009 at 11:02 am
    • Permalink

    @Erich

    What VMware product are you using as a host? Not all products support the drag and drop feature from the host side. I know the console with VMware Server, which I use predominantly, does not.

    • ax2009
    • Posted January 18, 2009 at 7:00 pm
    • Permalink

    The liburiparser package in the Ubuntu repository works for me

  1. I confirm this works! You are the man. I also do agree with that other guy your article is not new to linux friendly but more for an experienced linux user. Thanks so much

    • Z
    • Posted February 16, 2009 at 7:52 am
    • Permalink

    When running the vmware config it appeared to work as it said everything loaded successfully but it appears things are not perfect on boot up. This is what I see when I boot up the VM

    Starting VMWare Tools services in the virtual machine:
    Switching to guest configuration: done
    Guest filesystem dirver: failed
    Mounting HGFS shares: failed
    Guest memory manager: failed
    Guest vmxnet fast network device: failed
    Blocking file system: failed
    DMA setup: done
    Guest operating system daemon: done

  2. unbelievable guide, worked perfectly for me.. thanks very much for your help and time to figure this out

    this page is getting saved! :)

  3. Thank you, it works.

    • myystic
    • Posted February 22, 2009 at 5:19 pm
    • Permalink

    After 2 days of googling to make this work on Ububtu 8.10 …
    I found your post. I’m NooB to linux-ubuntu so it took a while, had some glitches, but all is running well now.

    Thank You Very Much!

  4. Inspired by your article, I copy-pasted your instructions into a simple installer shell, downloadable from:

    http://campodoro74.no-ip.org/wiki/files/open-vm-tools-810.sh

    just execute it (not using a SSH connection) with

    sh open-vm-tools-810.sh

    Thank you very much for your guide, it helped me a lot!

    Ah, I changed just 2 things:

    - ESX 3.5 VMware Tools are named VMwareTools-*.tar.gz

    - open-vm-tools are linked here: wget -nc http://garr.dl.sourceforge.net/sourceforge/open-vm-tools/open-vm-tools-2009.02.18-148847.tar.gz

  5. You are the man… that script work flawless, I even ran it a second after I upgraded my kernel and it work just fine as well!!!

    • Manfred
    • Posted March 1, 2009 at 4:10 am
    • Permalink

    Mumbles! Your docs look very promising and everything seems to work just fine for me until we get to the sudo ./vmware-install.pl where after a couple default acknowledged steps I get to “What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include]

    The above default directory does not exist. I know from uname -r that my current kernel is 2.6.27-7-server and if I look in the /usr/src firectory I can see such a named directory so I tried entering at this point of the vmware-install.pl prompt /usr/src/linux-headers-2.6.27-7-server/include

    I then get “the directory of kernel headers (version @@VMWARE@@ UTS_RELEASE) does not match your running kernel (version 2.6.27-7-server). Even if the modeule were to compile sucessfully it would not load into the running kernel”

    Any suggestions?

    The above error msg is the exact same one I get when I try to install the old vmware tools (i.e. without the vmware compiling steps as above). I followed the steps for desktop since I have 8.10 server installed – the setup F4 lite VM version, but then subsequently ia added x and gnome-core to my install)

    I have done both sudo apt-get install build-essential linux-headers-generic
    and sudo apt-get install build-essential linux-headers-2.6.27-7-server before attempting any of this.

    TIA

    • cccarey
    • Posted March 1, 2009 at 8:41 am
    • Permalink

    @Manfred

    Two suggestions:

    1) update your install prior to installing the tools. The latest kernel for 8.10 is 2.6.27-11.

    2) double check the build packages from the step right after downloading openvmtools are installed ( dpkg -l |grep packagename )

    • akintemel
    • Posted March 3, 2009 at 6:25 am
    • Permalink

    its was great ..thank you very much ..

    its work perfect :)

    • ebrogen
    • Posted March 6, 2009 at 4:51 pm
    • Permalink

    You Da’ Man!
    Works perfectly.

    • jamesW
    • Posted March 8, 2009 at 2:27 pm
    • Permalink

    You’re a legend!

    • Genís
    • Posted March 18, 2009 at 7:20 am
    • Permalink

    Thanks for the post and the script. Works perfect!!!!

  6. This was very helpful, as were the copies of the shell scripts on Github. However, whether I run the scripts, or go through them step-by-step, I am hitting the same snag with UriParser every time.

    Even with the successful install of uriparser 0.7.4, with header files at /usr/local/include, it never finds uriFreeQueryListA, which according to the configure script is just “a random function from libc, just to make sure the linker can find the library being tested”.

    I have tried this with the latest 3/18 build of open-vmware-tools also. This was a lot more work than I wanted to do just for Unity, so I finally gave into the –disable-unity option. It did work to get shared directories at /mnt/hgfs/, which is what I really needed.

    Lastly, all the “None of the pre-built vXXXX modules for VMWare Tools is suitable for running kernel” messages in the vmware-install.pl script are worth mentioning. There is still a lot of building that goes on. It felt as though I screwed something else up, until it all succeeded.

    Thanks!

    • Jacob McDonald
    • Posted March 22, 2009 at 6:37 pm
    • Permalink

    Awesome! Thanks so much for this. I searched and tried things for literally hours before I found your blog entry that worked perfectly!

    Oh, one small thing I had to do. I had to add the “–without-dnet” option to the open-vm-tools configure script.

    Here’s my config:

    Host: VMware ESX 3.5i
    Guest: Ubuntu 8.10 Server x64

    Cheers!

    • Ben Reid
    • Posted March 24, 2009 at 1:17 am
    • Permalink

    Great stuff – worked fine after a couple of tweaks. Thank you for your effort!

    My experiences (as at 24 March, kernel updated to 2.6.27-11 generic):

    1. Follow cccarey (commenter 18 above) – update your Ubuntu installation prior to compiling the open-vm-tools. (But if you’re reading this like me you probably didn’t, and got everything working, updated and broke it… ;-) )

    2. You can download a later version of the open-vm-tools sources (the blog post points to the previous version) (2009.03.18-154848):

    wget -c http://downloads.sourceforge.net/open-vm-tools/open-vm-tools-2009.03.18-154848.tar.gz?use_mirror=waix

    3. Follow Ryan Rickarts (commenter 23 above) if you get a problem with ./configure throwing up a message about uriParser not being the right version and cannot find uriFreeQueryListA: just run ./configure –disable-unity and you get the tools (minus Unity, of course…)

    • JK
    • Posted March 28, 2009 at 2:20 pm
    • Permalink

    As of this post, could not get it to work. All I wanted was cut and paste working.
    Using VMWare Fusion with Ubuntu 8.10 kernel 2.6.27-11. Used 2009-03.28 version of open-vm-tools source. Used the server-edition script with the latest version of open-vm-tools. Everything upgraded and installed ok. But still doesn’t work…

    • dmwp37
    • Posted March 29, 2009 at 11:36 pm
    • Permalink

    Hi, Ryan Rickerts

    you need to do this to remove the configuration error about uriparser

    export LDFLAGS=”-L/usr/local/lib”

    • rob
    • Posted April 9, 2009 at 9:58 am
    • Permalink

    very helpful – thanks!

    • Joseph S.
    • Posted April 24, 2009 at 10:20 am
    • Permalink

    Thank you very much for taking the time to maintain these instructions!

    • xoros
    • Posted April 27, 2009 at 1:02 pm
    • Permalink

    I get config error about uriparser too.
    I tried the export LDFLAGS=”-L/usr/local/lib”

    Now I get this error:
    configure: error: C compiler cannot create executables

    I also cannot mount or see the cdrom drive at all that contains the vmware tools.
    tar xvfz /media/cdrom/VMwareTools-*.tar.gz
    That tar statement just gives errors.

    Running 9.04 Jaunty x64

    Any help appreciated. thanks.

    • sholyer
    • Posted April 28, 2009 at 3:12 am
    • Permalink

    Thanks for maintaining a great post. It helped me get this going.

    I’m sure lots of folks have this working on Jaunty, but I wanted to confirm that these instructions work with a Jaunty guest (with VMWare Server running on Hardy Host).

    First, if the cdrom still has the install disk in it, jaunty won’t see the VMWareTools files. I think this might be a problem on other ubuntu releases too. Don’t forget to eject the install cd … I had mounted the install iso as a virtual CD and I had to stop the VM, map the virtual CD to the (empty) physical CD. Then restart the VM guest. Then the VMWareTools were there–just like they’re supposed to be.

    Also, I picked up the newest open-vm-tools and the newest uriparser libs (which both released around the same time as Jaunty–I thought why not be completely up to date). After several false starts I got that all to build … but the instructions here for tar’ing up the sources from open-vm-tools in the steps before running vmware-install.pl don’t work with the latest open-vm-tools version.

    It seems they moved the location of the .h files so the tar command you provided doesn’t grab them anymore. I was too lazyto figure out the necessary commands (though you’d already done the heavy lifting) so I went back to the previous version of open-vm-tools and uriparser (the one you link to here).

    Then everything worked like a charm.

    Two notes about “charm”:
    When building uriparser … for some reason on my machine the includes and the libs didn’t get stored in /usr/local but in build directory under ./include and ./.libs (note the hidden directory there). I could not get away from that dreaded unity check failing UNTIL I copied the includes and .libs by hand into the equivalent directories in /usr/local … (and no even with CFLAGS/CPPFLAGS/LDFLAGS adjusted to the “other” location, open-vm-tools configure didn’t find the libs). I don’t know why, but that finally worked for me.

    Don’t forget to set LDFLAGS=”-L/usr/local/uriparser” … no space after the L.

    • xoros
    • Posted April 29, 2009 at 1:11 pm
    • Permalink

    Where does it say in this guide what is being used as a guest?
    I am assuming Hardy is the host?

    I’m trying to run vmware server on Jaunty x64 host and Windows XP SP2 as a guest and still encounter the problems I mention.

    I guess there is no way for Jaunty to “see” the cdrom install of vmware tools on the Windows guest??

    • Corran C'hetano
    • Posted May 1, 2009 at 1:56 am
    • Permalink

    Man, this tool is just AMAZING. Please keep up with your brilliant work and keep it up-to-date! I will never fear a Kernel Update ever again;)
    Thank you!
    Is Jaunty next? ;)

    • Jordi
    • Posted June 3, 2009 at 11:02 am
    • Permalink

    Thanks!
    It worked perfectly on jaunty. The only thing I had to install on a clean jaunty server install was libpam0g-dev for the open-vm-tools configure.

    And, open-vm-tools-2009.05.22-167859 did not work for me

    • 3beezer
    • Posted July 22, 2009 at 3:26 pm
    • Permalink

    I followed these directions four times, but I’m still coming up short. Most things are working: network, cut-and-paste, automatic resizing of the guest window. However, the pointer is still hostage to the guest unless I use ctrl-alt to release it. I have previously been able to move the pointer smoothly from the guest to the host. Is that behavior no longer achievable?

    Also, I found that I have to run vmware-user in startup applications to get even the virtues I mentioned. No one else mentioned having to do the same, so I am even more suspicious that something is wrong here.

    • 3beezer
    • Posted July 22, 2009 at 5:22 pm
    • Permalink

    I followed the procedure in this HowTo four times but keep coming up short. Most features of VMware Tools work — drag-and-drop, resizing of the guest window, and networking — but the pointer is hostage to the guest. In previous installations, I was able to move the pointer continuously from the guest to the host. Is that behavior no longer achievable?

    Also, I found that I had to put the command /usr/bin/vmware-user in Startup Programs to get any of the features of VMware Tools. As no one else mentioned having to run this command, I wonder whether something else is wrong with my installation.

    BTW, my guest is actually Ubuntu 9.04 and the host is Kubuntu 9.04.

    • Cesar
    • Posted August 22, 2009 at 9:31 pm
    • Permalink

    Works perfectly!!! Thanks a lot!!!
    Regards from Peru,
    Cesar

    • Shelly
    • Posted August 26, 2009 at 8:20 am
    • Permalink

    Thanks. This guide helped me a lot.


3 Trackbacks/Pingbacks

  1. By February 21st, 2009 - Knives on 21 Feb 2009 at 1:23 am

    [...] HowTo: Install VMWare Tools on Ubuntu 8.10 (Intrepid) VMware Toolsが古くてそのままじゃインストールできないので Open Virtual Machine Toolsで下準備をしてからインストールしてあげるって感じみたい。 VMware内でページを開いてひたすらコピペしていけば終わるので楽ちん。 コピー&ペーストのためには”vmware-users”を起動しておく必要があるので適当な自動起動手段で処理。 今回はGNOMEじゃなくOpenBoxを使う事にしたので~/.config/openbox/autostart.shに追記することになった。 [...]

  2. [...] Installing VMWare Tools on Ubuntu 8.10 October 2, 2009 Paul Leave a comment Go to comments Instructions here: http://cccarey.wordpress.com/howtos/howto-install-vmware-tools-on-ubuntu-810-intrepid/ [...]

Post a Comment

*
*