VMware Tools installation fails to start the guest operating system daemon on 64-bit Linux Guest Operating Systems with the 32-bit glibc-common package installed (1023185)

 Details

VMware Tools require the 64-bit ldd (list dynamic dependencies) utility to configure the guest operating system daemon. The ldd utility requires the 64-bit glibc-common (GNU C common library) package to be installed. However, if the 32-bit glibc-common package is installed to overwrite the 64-bit glibc-common package, VMware Tools configuration fails to find the correct libraries for the guest operating system daemon.

Solution

The best practice is to install the 64-bit glibc-common package, not the 32-bit glibc-common package. However, if the 32-bit glibc-common package is required, perform this task.

Note: Certain applications, such as versions of Oracle, require the installation of the 32-bit glibc-common package. Therefore, re-installation of the 64-bit glibc-common package might cause such applications on 64-bit Linux operating systems to fail.

The workaround given is only for the installation and function of VMware Tools and should not interfere with or interrupt the operation of those applications.

1. Install VMware Tools, but do not run the vmware-config-tools.pl configuration program.
2. Link the necessary libraries. For example, these commands are appropriate when using the default installation paths:
   ln –s /usr/lib/vmware-tools/lib64/libdnet.so.1/libdnet.so.1 /lib64/libdnet.so.1
   ln –s /usr/lib/vmware-tools/lib64/libproc-3.2.7.so/libproc-3.2.7.so /lib64/libproc-3.2.7.so
   
   Note: Running chmod file_name 755 may be required on the lib files to complete the installation.
   
   
3. Run the vmware-config-tools.pl configuration program. For example:
   /usr/bin/vmware-config-tools.pl
   
   The paths /usr/lib/vmware-tools/lib64 and /usr/bin/vmware-config-tools.pl refer to the default installation paths. If you specify custom paths during installation, use those customized paths for the preceding task.