Which one should I prefer open-vm-tools or vmware

Latest response

Which I should choose open-vm-tools or provide by VMware vmware-tools ?

Vsphere 6.5 , 6 , 5.5

rhel 5,6,7


Please see this VMware KB article.

In a nutshell: if a Linux distribution provides open-vm-tools from the distribution's standard repository and that distribution/release is supported by VMware, VMware supports and actually prefers you to use that. For older releases that don't include open-vm-tools just use vmware-tools just as before.

For RHEL, that means open-vm-tools for all RHEL 7.x and newer, and vmware-tools for 5.x and 6.x.

Strong response as always Matti.

In addition, you need to enable EPEL repository to get open-vm-tools for RHEL 6. open-vm-tools for RHEL 7 is on the standard rhel-7-server-rpms repo.

Hello Yasar,

This is a very hard question to answer. If you search the VMWare Knowledge Base, you are lead to be leave that open-vm-tools should be used, but once installed Vsphere 5.5 claims open-vm-tools to be outdated. I have no experience with Vsphere 6 or 6.5.

I would go for the VMWare-tools of VMWare as long as they are available.

Advise: Check the VMWare Knowledge base for the current status. The VMWare community for Linux lead me to this article https://kb.vmware.com/s/article/2073803?language=en_US


Jan Gerrit Kootstra

From experience with vSphere 6, open-vm-tools works well on both RHEL 6 and RHEL 7.

For the combination of RHEL 7 and VMware ESXi 5.5 (Vsphere is the management tool), the VMware Compatibility Guide says that open-vm-tools is supported (Recommended) while the vmware-tools is listed as just supported.

That leads me to believe that Vsphere 5.5 does not quite include the ability to recognize the open-vm-tools: Ithink it works along the lines of "if it's not the latest version of the official VMware Tools I know about, it's outdated". When Vsphere 5.5 was being developed, open-vm-tools did not quite exist yet as a released package, so it's understandable.

I just discovered open-vm-tools because we are having issues when upgrading VMWare Tools for RHEL5 x32 systems, that we are trying to migrate away from. For some reason, even after I unmount the ISO from the OS, it still has it mounted on vSphere and we have issues with vMotion and have to power them off to move to a different host.

I'm wondering if open-vm-tools performs better then VMWareTools which comes with vSphere? Or if there are pros and cons?

Hello Christopher,

In general umount of an external media like a DVD, CD or an USB media does not release the device it is put in. eject /dev/.... is the way to release the device. On a physical server eject/dev/dvd would open the drawer.


Jan Gerrit

Jan, so if I'm understanding you correctly, instead of running the following command to umount the VMWare Tools ISO:

umount /mnt/dvd

Instead we would run the following?

eject /mnt/dvd

I was not aware of the eject command. I wonder if this is where the issues is, since I'm just using the umount command.

And again, I did not know about the eject command.

Sorry Christopher,

It seems your question never reached my mailbox:

eject /mnt/dvd

VMotion can cause issues if you only run

umount /mnt/dvd

eject command is part of eject rpm.


Jan Gerrit

After upgrading the kernel for a RHEL6 to 2.6.32-696.16.1.el6, for some reason, VMWare Tools (v 10.1.10 would not upgrade), no error message once the install completed and summary in vSphere shows not installed.

I wanted to use open-vm-tools instead to try it, looks like there is only a repo from RedHat for RHEL7, and would have to use EPEL for RHEL6. It would take some time to get this setup in order for me to use this repo due to our security, so I had just grab the newest iso from VMWare.

So wanted to share my experience with others.


Hi All I am having issues with VMware-tools running on Red Hat 6. Whenever kernel gets updated, I will get a below errors Entering non-interactive startup /etc/rc3.d/S00check-vmware-tools: line 10: syntax error near unexpected token start' /etc/rc3.d/S00check-vmware-tools: line 10: start)' the status VMware changes to installed not running. so every time this happens, I need to recompile it by running /usr/bin/vmware-config-tools.pl I have another red hat 6 and opev-vm-tools installed, there is no issue at all. I am planning to remove VMware tools and replace to open-VM-tools. somehow, I cannot locate open-vm-tools rpm. Any suggestion where I can get them?

open-vm-tools rpm for RHEL 7 is in the base repository, and therefore supported by Red Hat.

open-vm-tools rpm for RHEL 6 is in the EPEL repository (not provided by Red Hat), and therefor not supported by Red Hat.

Source: https://access.redhat.com/solutions/1694373

I tried to install open-vm-tools rpm via the EPEL repository for RHEL 6.5 x64. However it suggests it needs the "libxmlsec1.so.1 64bit" and "xmlsec1-openssl" but I cant find those rpms? any ideas how to get around these dependencies

Hi Steve,

  dependency: xmlsec1-openssl
   provider: xmlsec1-openssl.i686 1.2.20-4.el6
   provider: xmlsec1-openssl.x86_64 1.2.20-4.el6

  dependency: libxmlsec1.so.1()(64bit)
   provider: xmlsec1.x86_64 1.2.20-4.el6

Installing xmlsec1.x86_64 and xmlsec1-openssl.x86_64 will provide those dependencies.

I have a similar question RHEL 7 ( 7.5 and 7.6 based) Vsphere 6.5 , 6 , 5.5, and Hyper-V 2016 , later 2019

Will be using Scsi Controller as "Vmware ParaVirtual".


the latest version of open-vm-tools on rhel-7-server-rpms repository is "open-vm-tools-10.3.10-2.el7_8.1.x86_64", but there is a newer version for ESXI 6.7 if you install tools from de Vcenter (10.3.21). Are you going to upload a newer version of open-vm-tools to the official repos?


The source contains updates: https://github.com/vmware/open-vm-tools/releases

On RHEL7, I see: v.10.3.10 On RHEL8, I see: v.11.0.0

I guess you need to update or be patient? @RedHat could you please provide some feedback on when the RHEL7 package will be updated?

Red Hat does not generally keep their packages 100% up-to-date with the "upstream" (source) version; rather, they "back-port" only the specific patches needed to provide security or critical bug fixes into an updated build of the same version of the package which is already in RHEL X.Y.

So, for your example, RHEL 7.8 systems will generally run "open-vm-tools-10.3.10" at least until RHEL 7.9 ships. If there are critical patches needed before then (e.g. security issues or crashing bugs), they may release "open-vm-tools-10.3.10-3.el7_8.2.x86_64" (note the bumps from "-2" to "-3" and "7_8.1" to "7_8.2") with the fixed code from 10.3.21 ported back to 10.3.10.

For what it's worth, we've just started our first ESXi 6.7 cluster, and it is running a few test VMs just fine with the "old" RHEL 7.x version of open-vm-tools. If you did actually run into a crashing bug or significant performance problem due specifically to the older version of open-vm-tools, you should open a support case with Red Hat (# of tickets opened is really the only concrete data they have to tell the difference between a "serious problem" (to fixed ASAP) or a "minor annoyance" (probably won't be fixed until RHEL 7.9).

Thank you very much for your answers. We wanted to be sure what the latest version is. We are going to start our annual systems patch and want to go to the newest version possible.

Our doubt has been resolved.

Thanks again