-**Updated on: 17 OCT 2019**
+t's in the Release Notes
-VMware Tools | 17 OCT 2019 | Build 14773994
+The release notes cover the following topics:
-Check for additions and updates to these release notes.
+* [Before You Begin](#beforeyoubegin)
+* [Internationalization](#i18n)
+* [Compatibility Notes](#compatibility)
+* [Guest Operating System Customization Support](#guestop)
+* [Interoperability Matrix](#interop)
+* [Installation and Upgrades for This Release](#installupgrade)
+* [Resolved Issues](#resolvedissues)
+* [Known Issues](#knownissues)
-What's in the Release Notes
----------------------------
+## Before You Begin
-The release notes cover the following topics:
+**Important note about upgrading to ESXi 6.0 or later**
-* [What's New](#whatsnew)
-* [Before You Begin](#beforeyoubegin)
-* [Internationalization](#i18n)
-* [Product Support Notice](#productsupport)
-* [End of Feature Support Notice](#endoffeaturesupport)
-* [Compatibility Notes](#compatibility)
-* [Guest Operating System Customization Support](#guestop)
-* [Interoperability Matrix](#interop)
-* [Known Issues](#knownissues)
+Resolution on incompatibility and general guidelines: While upgrading ESXi hosts to ESXi 6.0 or later, and using older versions of Horizon View Agent, refer to the knowledge base articles:
-What's New
-----------
+* [Connecting to View desktops with Horizon View Agent 5.3.5 or earlier hosted on ESXi 6.0 or later fails with a black screen.](http://kb.vmware.com/kb/2144438)
+* [Connecting to View desktops with Horizon View Agent 6.0.x or 6.1.x hosted on ESXi 6.0 or later fails with a black screen.](http://kb.vmware.com/kb/2144518)
+* [Connecting to View desktops with Horizon View Agent 6.1.x hosted on ESXi 6.0 or later fails with a black screen.](http://kb.vmware.com/kb/2144453)
-* It is highly recommended to upgrade to this version of VMware Tools, if you are using the native service discovery feature in vRealize Operations Manager 8.0, or using the vRealize Operations Service Discovery Management Pack with previous releases of vRealize Operations Manager (7.x or before). For more details, refer [KB 75122](https://kb.vmware.com/s/article/75122).
+## Internationalization
-Before You Begin
-----------------
+VMware Tools 11.0.5 is available in the following languages:
-**Important note about upgrading to ESXi 6.0 or later**
+* English
+* French
+* German
+* Spanish
+* Italian
+* Japanese
+* Korean
+* Simplified Chinese
+* Traditional Chinese
-Resolution on incompatibility and general guidelines: While upgrading ESXi hosts to ESXi 6.0 or later, and using older versions of Horizon View Agent, refer to the knowledge base articles:
+## Compatibility Notes
-* [Connecting to View desktops with Horizon View Agent 5.3.5 or earlier hosted on ESXi 6.0 or later fails with a black screen.](http://kb.vmware.com/kb/2144438)
-* [Connecting to View desktops with Horizon View Agent 6.0.x or 6.1.x hosted on ESXi 6.0 or later fails with a black screen.](http://kb.vmware.com/kb/2144518)
-* [Connecting to View desktops with Horizon View Agent 6.1.x hosted on ESXi 6.0 or later fails with a black screen.](http://kb.vmware.com/kb/2144453)
+* Starting with VMware Tools version 10.2.0, Perl script-based VMware Tools installation for FreeBSD has been discontinued. FreeBSD systems are supported only through the open-vm-tools packages directly available from FreeBSD package repositories. FreeBSD packages for open-vm-tools 10.1.0 and later are available from FreeBSD package repositories.
-Internationalization
---------------------
+## Guest Operating System Customization Support
-open-vm-tools 11.0.1 is available in the following languages:
+The [Guest OS Customization Support Matrix](http://partnerweb.vmware.com/programs/guestOS/guest-os-customization-matrix.pdf) provides details about the guest operating systems supported for customization.
-* English
-* French
-* German
-* Spanish
-* Italian
-* Japanese
-* Korean
-* Simplified Chinese
-* Traditional Chinese
+## Interoperability Matrix
-End of Feature Support Notice
------------------------------
+The [VMware Product Interoperability Matrix](http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php) provides details about the compatibility of current and earlier versions of VMware Products. The [VMware Product Interoperability Matrix](http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php) of VMware Tools 11.0.0 can be applied to VMware Tools 11.0.5.
-* The tar tools (linux.iso) and OSPs shipped with VMware Tools 10.3.5 release will continue to be supported. However, releases after VMware Tools 10.3.5 will only include critical and security fixes and no new feature support in these types of VMware Tools (tar tools and OSP's). It is recommended that customers use open-vm-tools for those operating systems that support open-vm-tools. For more information on different types of VMware Tools, see [https://blogs.vmware.com/vsphere/2016/02/understanding-the-three-types-of-vm-tools.html](https://blogs.vmware.com/vsphere/2016/02/understanding-the-three-types-of-vm-tools.html)
+## Installation and Upgrades for this release
-Compatibility Notes
--------------------
+VMware Tools can be downloaded from the [Product Download](https://my.vmware.com/web/vmware/details?downloadGroup=VMTOOLS1105&productId=742) page.
-* Starting with VMware Tools version 10.2.0, Perl script-based VMware Tools installation for FreeBSD has been discontinued. FreeBSD systems are supported only through the open-vm-tools packages directly available from FreeBSD package repositories. FreeBSD packages for open-vm-tools 10.1.0 and later are available from FreeBSD package repositories.
+The steps to install VMware Tools vary depending on your VMware product and the guest operating system you have installed. For general steps to install VMware Tools in most VMware products, see [General VMware Tools installation instructions (1014294)](http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1014294).To set up productLocker to point to the shared datastore, see [KB 2004018](https://kb.vmware.com/kb/2004018).<br>
+<br>
+For specific instructions to install, upgrade, and configure VMware Tools, see the VMware Tools [Documentation](https://www.vmware.com/support/pubs/vmware-tools-pubs.html) page.
-Guest Operating System Customization Support
---------------------------------------------
+## Resolved Issues
-The [Guest OS Customization Support Matrix](http://partnerweb.vmware.com/programs/guestOS/guest-os-customization-matrix.pdf) provides details about the guest operating systems supported for customization.
+* **DNS server is reported incorrectly as '127.0.0.53' when using systemd-resolved.** DNS server is reported incorrectly in GuestInfo as '127.0.0.53' , when the OS uses systemd-resolved. This issue is fixed in this release.
+
+## Known Issues
+
+* **In Linux guests, when /tmp is mounted with "noexec" option, any solution that depends on running a program or script stored under /tmp inside the guest using VMware Tools fails.** In Linux guests, when is mounted with "noexec" option, any solution that depends on running a program or script stored under inside the guest using VMware Tools fails.
+ Workaround: Override TMPDIR environment variable for service to a different path with executable permissions. However, this workaround is lost due to guest OS or VMware Tools upgrade. In this version of VMware Tools, can be used to override the environment variables for instances as following: Note: Environment settings are applied when starts up. So, vmtoolsd needs restart for new settings to take effect.
+* **Drag functionality fails to work in Ubuntu.** Drag functionality fails to work in Ubuntu 16.04.4 32-bit virtual machine installed using easy install. Also, failure of copy and paste functionality is observed in the same system. Note: This issue is applicable for VMware Tools running on Workstation and Fusion. Workaround:
+ - Add the linux kernel boot option.
+ - To gain access to larger resolutions, remove option from the file.
+* **Shared Folders mount is unavailable on Linux VM.** If the **Shared Folders** feature is enabled on a Linux VM while it is powered off, shared folders mount is not available on restart. Note: This issue is applicable for VMware Tools running on Workstation and Fusion. Workaround: If the VM is powered on, disable and enable the **Shared Folders** feature from the interface.<br>
+For resolving the issue permanently, edit **/etc/fstab** and add an entry to mount the Shared Folders automatically on boot.<br>
+For example, add the line:
-Interoperability Matrix
------------------------
-
-The [VMware Product Interoperability Matrix](http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php) provides details about the compatibility of current and earlier versions of VMware Products.
-
-Resolved Issues
----------------
-
-* **Memory leak in vmtoolsd.**
-
- vmtoolsd leaks memory when the vSphere APIs ListGuestAliases and ListGuestMappedAliasers are used.
-
- This issue is fixed in this release.
-
-Known Issues
-------------
-
-* **Suspend Guest of Linux VM using any version of open-vm-tools may fail with some versions of SELinux.**
-
- A "Suspend Guest" operation on a Linux guest running any version of open-vm-tools and with SELinux enabled may stall and ultimately fail.
-
- The failure may appear as:
- - a "Failed to suspend the virtual machine" message display.
- - nothing happened and the "Suspend Guest" button is reactivated. IPv4 connections may be closed.
- - a delayed suspend happens but the IPv4 addresses are lost when the VM is resumed.
-
- Even an apparent "stall" which exceeds 30 seconds is an indication of the problem.
-
- For more details, see [KB 74722](https://kb.vmware.com/s/article/74722).
-
- Workaround:
-
- Update the selinux-policy and selinux-policy-targeted packages to the latest version available from the Linux vendor. If package updates are not available or if the issue persists, then consider the following workaround:
-
- Create an exemption for the vmtools/NetworkManager denied access by using the audit2allow command to generate a local loadable SELinux policy module as outlined in [KB 74722](https://kb.vmware.com/s/article/74722).
-
-* **Drag functionality fails to work in Ubuntu.**
-
- Drag functionality fails to work in Ubuntu 16.04.4 32-bit virtual machine installed using easy install. Also, failure of copy and paste functionality is observed in the same system.
-
- Note: This issue is applicable for open-vm-tools running on Workstation and Fusion.
-
- Workaround:
-
- * Add the modprobe.blacklist=vmwgfx linux kernel boot option.
- * To gain access to larger resolutions, remove svga.guestBackedPrimaryAware = "TRUE" option from the VMX file.
-* **Shared Folders mount is unavailable on Linux VM.**
-
- If the **Shared Folders** feature is enabled on a Linux VM while it is powered off, shared folders mount is not available on restart.
-
- Note: This issue is applicable for open-vm-tools running on Workstation and Fusion.
-
- Workaround:
-
- If the VM is powered on, disable and enable the **Shared Folders** feature from the interface.
- For resolving the issue permanently, edit **/etc/fstab** and add an entry to mount the Shared Folders automatically on boot.
- For example, add the line:
- vmhgfs-fuse /mnt/hgfs fuse defaults,allow\_other 0 0
-
+ vmhgfs-fuse /mnt/hgfs fuse defaults,allow_other 0 0
* Import 2007.10.08 snapshot, which includes patches to fix the
--without-x flag, and compilation with gcc 4.2.
+commit 85b51e8d8fecf8cb6e8408c977b98bb5e06b22f2
+Author: Oliver Kurth <okurth@vmware.com>
+Date: Wed Dec 11 10:19:09 2019 -0800
+
+ Avoid vmtoolsd crash in HostInfo.
+
+ The guest identification code causes vmtoolsd to crash in certain
+ versions of some distros. The crash is caused by recent changes to
+ the lsb_release command. Previously, if the command existed, all
+ of its options worked. Now, some of the options no longer exist.
+
+ Change the code to check for an lsb_release failure whenever it is
+ invoked.
+
+ Fix for: https://github.com/vmware/open-vm-tools/issues/390
+
+commit 71aef05d01c2118f85e1a1994d464f36d10b1c7e
+Author: Oliver Kurth <okurth@vmware.com>
+Date: Wed Dec 11 10:19:09 2019 -0800
+
+ dndUIX11.cpp::GetLastDirName() Remove a trailing slash in a directory pathname.
+
+commit 9fc7af4598442fdd2b8e9c0f28e27e546209e01e
+Author: Oliver Kurth <okurth@vmware.com>
+Date: Wed Dec 11 10:19:09 2019 -0800
+
+ Configurable environment for vmtoolsd.
+
+ If a user wants to override(*) an environment variable e.g.
+ TMPDIR for vmtoolsd, the only choices for the user are:
+ 1. Change system environment variable, that may affect more
+ than vmtoolsd
+ 2. Change vmtoolsd service startup scripts on Linux.
+ Some of these methods, especially #2 gets overwritten by
+ upgrades and user is forced to re-apply the change on every
+ upgrade of VMTools. Also, #2 is somewhat complex due to
+ different type of VMTools installations and differences
+ in Linux distros.
+
+ We can't override the environment completely from within
+ service but we can configure the environment to a large
+ extent once vmtoolsd comes up and reads tools.conf.
+
+ *=> "override" term here applies to setting, modifying and/or
+ unsetting an environment variable.
+
+ This is mainly required for system service vmsvc, but
+ given that vmusr shares code with vmsvc, we can provide
+ this functionality for both.
+
+ Updated example tools.conf with the new configuration.
+
+commit e6bc102b12eb346eb0c77feca50ff185994bbcab
+Author: Oliver Kurth <okurth@vmware.com>
+Date: Wed Dec 11 10:19:09 2019 -0800
+
+ nicinfo: report real nameservers used when using systemd-resolved
+
+ If systemd-resolved is used, report the external DNS server, not the
+ locally installed one. This is detected by checking if /etc/resolv.conf
+ is a link to /run/systemd/resolve/stub-resolv.conf. In that case,
+ /run/systemd/resolve/resolv.conf will hold the actual DNS server. See
+ https://www.freedesktop.org/software/systemd/man/systemd-resolved.service.html
+
+commit 93c2d3b8c943ab2ce5a3d75b1b02a51af6705f54
+Author: Oliver Kurth <okurth@vmware.com>
+Date: Wed Dec 11 10:19:09 2019 -0800
+
+ Fix Coverity reported issue in dndUIX11.cpp
+
+ - unsigned_compare: This greater-than-or-equal-to-zero comparison of an
+ unsigned value is always true. end >= 0UL.
+ Function: GetLastDirName
+
+commit dab6d43fcb1b5a2f31b5e160c780a0dd4f1a03b7
+Author: Oliver Kurth <okurth@vmware.com>
+Date: Wed Dec 11 10:19:09 2019 -0800
+
+ [open-vm-tools Coverity] Fix Coverity scan reported issues in copyPasteUIX11.cpp
+
+ - Non-static class member mHGGetListTime is not initialized in this constructor
+ solution: add it into init list of constructor
+
+ - unsigned_compare: This greater-than-or-equal-to-zero comparison of an
+ unsigned value is always true. end >= 0UL.
+ Function: GetLastDirName
+
+commit ab090e4b20b80f3a1f3dc47a096650232a4588ee
+Author: Oliver Kurth <okurth@vmware.com>
+Date: Wed Dec 11 10:19:08 2019 -0800
+
+ Remove residual data when the DNS nameserver configuration changes.
+
+ If the list of DNS nameservers available should shorten or both IPv4 and
+ IPv6 entries are present, residual data can still be available for display.
+ This change to nicInfoPosix.c corrects the problem.
+
+commit fcaa29ff7269cb73002db455f7d7e6bd8de29d3c
+Author: Oliver Kurth <okurth@vmware.com>
+Date: Wed Dec 11 10:19:08 2019 -0800
+
+ Tools-11.0.5 - Trim trailing whitespace from log params in /etc/tools.conf.
+
+ Remove trailing whitespace from pathnames and parameters in
+ tools.conf.
+
+commit 08f1a0270922b53e9309cf5d0a253c3df3dcc508
+Author: Oliver Kurth <okurth@vmware.com>
+Date: Wed Dec 11 10:19:08 2019 -0800
+
+ Avoid securing disk device info for ZFS pools (at this time)
+
+ ZFS filesystem pools device names can appear as single directory name
+ at the root directory. The current logic to locate the
+ /sys/class/blocks/<device> PCI structure based on typical device name
+ format will fail for ZFS pools. As an immediate fix to the SIGSEGV,
+ avoid attempting to locate the PCI info; keep vmtoolsd running.
+
+ Addresses https://github.com/vmware/open-vm-tools/issues/378
+
+commit 7c09ff48397af1ea7c33d37018ed01a46338beb4
+Author: Oliver Kurth <okurth@vmware.com>
+Date: Wed Oct 30 11:21:53 2019 -0700
+
+ Common source file change not directly applicable to open-vm-tools.
+
+commit 86d3256f2acccc066648e6b25e16b46930338406
+Author: Oliver Kurth <okurth@vmware.com>
+Date: Wed Oct 30 11:21:53 2019 -0700
+
+ stop systemd-243 udev complaints #371
+
+ Address issues from pull request #371 on github:
+ - fix substiution variables for systemd-243
+ - fix permissions of rules file
+ See https://github.com/vmware/open-vm-tools/pull/371
+
+commit 9dd1f856cff25e27b01905118d2e34997c6c93e5
+Author: Oliver Kurth <okurth@vmware.com>
+Date: Wed Oct 30 11:21:53 2019 -0700
+
+ Suppress a couple of coverity false alarms in FileLoggerOpen().
+
+ The stat() system call is used to determine whether to rotate logs.
+ There is no danger of time-of-check vs. time-of-use because the rotation
+ decision still holds even under the very-unlikely condition that the existing
+ log file size changes.
+
+ When rotating the logs, the service should not stop when a rename() fails
+ on an old file. The process ignores the rename() return code intentionally.
+ The error condition cannot be logged because the process is already in the
+ log handling context and would either crash or risk a recursion loop
+ otherwise. In addition, writing to stdout/stderr is useless, since the
+ process is running as a service and the stdout/stderr is reopened on /dev/null.
+
+ Therefore, the above two coverity issues are suppressed in the code.
+
+commit 7f7686fbcebe957608b32ef9cc9f9378a7ab33ca
+Author: Oliver Kurth <okurth@vmware.com>
+Date: Wed Oct 30 11:21:53 2019 -0700
+
+ Bump the VMware Tools version to 11.0.5 on vmtools-prod-cpd.
+
+ Update bora/public/vm_tools_version.h to set the current tools version
+ to 11.0.5
+
+ TOOLS_VERSION_SLEDGEHAMMER_UPDATE1 --> 11.0.5
+
+commit d3edfd142a81096f9f58aff17d84219b457f4987
+Author: Oliver Kurth <okurth@vmware.com>
+Date: Mon Oct 21 14:58:04 2019 -0700
+
+ update version to 11.0.1
+
+commit 11b3bfc92545dde7ebff483e795d767158a8be0d
+Author: Oliver Kurth <okurth@vmware.com>
+Date: Mon Oct 21 14:57:31 2019 -0700
+
+ update ChangeLog
+
+commit 2b4823913e889a9ee834470e5198964071093d7c
+Author: Oliver Kurth <okurth@vmware.com>
+Date: Mon Oct 21 14:57:07 2019 -0700
+
+ update Release Notes
### Initialization
###
-TOOLS_VERSION="11.0.1"
+TOOLS_VERSION="11.0.5"
AC_INIT(
[open-vm-tools],
- [11.0.1],
+ [11.0.5],
[open-vm-tools-devel@lists.sourceforge.net])
# In order to make this configure script auto-detect situations where
#define BUILD_NUMBER \
- "build-14773994"
+ "build-15389592"
#define BUILD_NUMBER_NUMERIC \
- 14773994
+ 15389592
#define BUILD_NUMBER_NUMERIC_STRING \
- "14773994"
+ "15389592"
#define PRODUCT_BUILD_NUMBER \
- "product-build-15528"
+ "product-build-17716"
#define PRODUCT_BUILD_NUMBER_NUMERIC \
- 15528
+ 17716
#define PRODUCT_BUILD_NUMBER_NUMERIC_STRING \
- "15528"
+ "17716"
/*********************************************************
- * Copyright (C) 2006-2019 VMware, Inc. All rights reserved.
+ * Copyright (C) 2006-2020 VMware, Inc. All rights reserved.
*
* This program is free software; you can redistribute it and/or modify it
* under the terms of the GNU Lesser General Public License as published
* Updating them therefore may require updating translations and vmsg
* auditing files in bora/messages/ to avoid breaking the build.
*/
-#define COPYRIGHT_YEARS "1998-2019" /* See the note above when changing. */
+#define COPYRIGHT_YEARS "1998-2020" /* See the note above when changing. */
#define COPYRIGHT_STRING "Copyright (C) " COPYRIGHT_YEARS " " COMPANY_NAME
#define RIGHT_RESERVED "All rights reserved."
projects / thirdparty / open-vm-tools.git / commitdiff
