This release contains general and security-only bulletins. Security-only bulletins are applicable to new security fixes only. No new bug fixes are included, but bug fixes from earlier patch and update releases are included.
If the installation of all new security and bug fixes is required, you must apply all bulletins in this release. In some cases, the general release bulletin will supersede the security- only bulletin. This is not an issue as the general release bulletin contains both the new security and bug fixes.
A few of the Issues resolved in this patch:
- The IBM BladeCenter HS23 server that boots from a USB device is unable to write the coredump file when the active coredump partition is configured on an USB device.A purple screen displays the dump attempting to initiate but does not complete.
- When a virtual machine is deployed from template or cloned with guest customization and the VMware Tools Upgrade Policy is set to allow the VM to automatically upgrade VMware Tools at next power-on, VMware Tools might fail to automatically upgrade during the first power-on operation of the VM.
- SNMP version 2 64-bit counters with high I/O on the interface might be reset when their values reach 2^32=4294967296, which is the maximum limit of a 32 bit counter.
- The performance chart on vSphere Client might display incorrect CPU usage statistics for Usage in MHz and Usage metrics.
- When you remap the source ports to a physical Network Interface Controller (pNIC) using the load-balancing algorithm Route based on physical NIC load, you might observe the regular packets passing through the newly mapped pnic before the Reverse Address Resolution Protocol (RARP).
- When a virtual machine is deployed from template or cloned with guest customization and the VMware Tools Upgrade Policy is set to allow the VM to automatically upgrade VMware Tools at next power-on, VMware Tools might fail to automatically upgrade during the first power-on operation of the VM.
- If you add a new virtual adapter to vSphere Distributed Switch (vds) on an ESXi host configured to use a vds, the vmkernel.log file might log an error message similar to the following: etherswitch: ESVsiGetParamPortCfg:392: : not found
- Higher storage latency values are observed on datastores presented from iSCSI based storage array when the TCP Offload Engine Chimney option is enabled on the array side.
- When you upgrade the Vmware Tools on a 64-bit Windows guest operating system, the tools.conf file removed automatically. After you apply this patch the tools.conf is retained by default.
More Details here