CentOS 6.2 VMware Tools Install the Easy Way

No internet tools install
Initiate the VMware tools install on your CentOS 6.2 VM. Open a SSH session to your VM and copy/paste this:
(It is not recommended to directly paste something into a command prompt as a malicious website can inject crazy business. Please paste this into notepad before putting it into a ssh session.)

yum -y install perl
mkdir /mnt/cdrom
mount /dev/cdrom /mnt/cdrom
cp /mnt/cdrom/VMwareTools-*.tar.gz /tmp
umount /mnt/cdrom
tar -zxf /tmp/VMwareTools-*.tar.gz -C /tmp
cd /
./tmp/vmware-tools-distrib/vmware-install.pl --default
rm -f /tmp/VMwareTools-*.tar.gz
rm -rf /tmp/vmware-tools-distrib

Bam! VMware Tools installed!

Network Tools install
# go to http://packages.vmware.com/tools/esx/index.html and find your version of ESX. Find the correct rpm and plug it into the script. I’ve left the example given by the mysterious Nathan M! Thank you Nathan!

yum -y install http://packages.vmware.com/tools/esx/5.5p01/repos/vmware-tools-repo-RHEL6-9.4.0-1.el6.x86_64.rpm
yum -y install vmware-tools-esx-nox

Advertisements

60 thoughts on “CentOS 6.2 VMware Tools Install the Easy Way

  1. Wow! Great article as I was dreading installing this on all of our development CentOS vm’s. Thanks for posting this!

    1. yum -y install perl
      #Install perl using yum

      mkdir /mnt/cdrom
      #Create a directory of ‘cdrom’ in the location of /mnt

      mount /dev/cdrom /mnt/cdrom
      #Mount the VMWareTools CD-ROM located @ /dev/cdrom to the folder /mnt/cdrom

      cp /mnt/cdrom/VMwareTools-*.tar.gz /tmp
      #Copy the VMWareTools tar.gz file to directory /tmp

      umount /mnt/cdrom
      #Unmount “/dev/cdrom” from “/mnt/cdrom”

      tar -zxf /tmp/VMwareTools-*.tar.gz -C /tmp
      #Extract contents of “/tmp/VMwareTools-*.tar.gz” (Documentation on the operators used can be found here: http://www.computerhope.com/unix/utar.htm)

      cd /
      #Change working directory to root

      ./tmp/vmware-tools-distrib/vmware-install.pl –default
      #In a new bash shell, execute the script located at “/tmp/vmware-tools-distrib/vmware-install.pl” with the operator “–default” (execute “./tmp/vmware-tools-distrib/vmware-install.pl –help” to see what the –default parameter does)

      rm -f /tmp/VMwareTools-*.tar.gz
      #Forefully remove the directory “/tmp/VMwareTools-*.tar.gz”

      rm -rf /tmp/vmware-tools-distrib
      #Recursively and forcefully remove the directory “/tmp/vmware-tools-distrib

      Hope that helped mate!

  2. Thanks for this, worked perfectly on the CentOS dev VM I was building today. I’m going to do a short post on a few other useful commands \ configs I had to do and would like to link back to your instructions if that’s OK?

  3. You are an angel! I have been trying to figure this out for hours (new to Linux AND feeling really stupid). Thanks a million.

  4. There was one REALLY annoying step before this.. I had no network to be able to install perl!
    So, before you can yum, you need to make sure the network adapter you choose for your vm is VMXNET3 and not E1000 which I had 🙂

  5. cp /mnt/cdrom/VMwareTools-*.tar.gz /tmp

    yields:

    cp: cannot stat `/mnt/cdrom/VMwareTools-*.tar.gz’: No such file or directory

    any tips?

  6. I get -bash: ./tmp/vmware-tools-distrib/vmware-install.pl: Permission denied on step: ./tmp/vmware-tools-distrib/vmware-install.pl –default

    any ideas? Running 6.4 release

    1. Make sure you are logged in as root so there isn’t a permission problem:
      sudo su –
      and then run the command again. If that doesn’t work:
      chmod 777 /tmp/vmware-tools-distrib/vmware-install.pl
      That makes the script have totally open permissions. Try again.

  7. Hi Greg, got this message when launching /tmp:vmware-tools-distrib/vmware-install.pl (-bash: /tmp/vmware-tools-distrib/vmware-install.pl: /usr/bin/perl: bad interpreter: no such file or directory); I verfy and everithing is ok. Do I miss something?
    Thanks in advance

  8. Any experience with doing it on later releases of Centos 6 (6.6 / 6.7). Also, is a reboot required? Considering rolling this out across the board as an upgrade on our production clusters.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s