VMware ESXi 5.5, Patch ESXi550-201509202-UG: Updates tools-light (2110233)
Release date: Sep 16, 2015
|Build||For build information, see KB 2110231.|
|Host Reboot Required||No|
|Virtual Machine Migration or Shutdown Required||No|
|PRs Fixed||1088789, 1214453, 1214632, 1218198, 1261811, 1319645, 1320301, 1326580, 1352240, 1412799|
|Related CVE numbers||NA|
Summaries and Symptoms
This patch updates the tools-light VIB to resolve the following issues:
- On a Linux virtual machine, the VMware Tools service, vmtoolsd, might fail when you shut down the guest operating system.
- Attempts to upgrade VMware Tools on a Windows 2000 virtual machine might fail with an error message similar to the following written to the vmmsi.log file:
Invoking remote custom action. DLL: C:\WINNT\Installer\MSI12.tmp, Entrypoint: VMRun
VM_CacheMod. Return value 3.
PROPERTY CHANGE: Deleting RESUME property. Its current value is '1'.
INSTALL. Return value 3.
- On an ESXi 5.5 host, some of the drivers installed on Solaris 11 guest operating system might be from Solaris 10. As a result, the drivers might not work as expected.
- When you attempt to configure VMware Tools with new kernel using the /usr/bin/vmware-config-tools.pl -k <kernel version> script after the kernel has been updated with Dracut, the driver list in add_drivers entry of /etc/dracut.conf.d/vmware-tools.conf file gets truncated. This issue occurs when the VMware Tools are upstreamed in the kernel.
- A Linux virtual machine enabled with Large Receive Offload (LRO) functionality on VMXNET3 device might experience packet drops on the receiver side when the Rx Ring #2 runs out of memory, since the size of Rx Ring#2 is unable to be configured originally.
- When you upgrade the Vmware Tools in 64-bit Windows guest operating system, the tools.conf file gets removed automatically. The tools.conf file will be retained by default from ESXi 5.5 Update 3 release onwards.
- After installing VMware Tools on Windows 8 or Windows Server 2012 guest operating system, attempts to open telnet using the start telnet://xx.xx.xx.xx command fails with the following error message
Make sure the virtual machine's configuration allows the guest to open host applications
- When you power off a virtual machine immediately after an install, upgrade or uninstall of VMware Tools in a Linux environment (RHEL or Cent OS 6), the guest OS might fail during the next reboot due to corrupted RAMDISK image file. The guest OS reports an error similar to the following:
RAMDISK: incomplete write (31522 != 32768)
Kernel panic - not syncing : VFS: Unable to mount root fs on unknown-block(0,0)
This release resolves the complete creation of the initramfs file creation during an install, upgrade or uninstall of VMware Tools.
Guest OS with corrupted RAMDISK image file can be rescued to complete boot state. For more information, see Knowledge Base article 2086520.
- During a High Availability failover or host crash, the .vswp files of powered ON virtual machines on that host might be left behind on the storage. When many such failovers or crashes occur, the storage capacity might become full.
- IPv6 Router Advertisements (RA) does not function as expected when tagging 802.1q with VMXNET3 adapters in an Linux virtual machine as the IPv6 RA address intended for the VLAN interface is delivered to the base interface.
Patch Download and Installation
The typical way to apply patches to ESXi hosts is through the VMware Update Manager. For details, see the Installing and Administering VMware vSphere Update Manager.
ESXi hosts can be updated by manually downloading the patch ZIP file from the VMware download page and installing the VIB by using the esxcli software vib command. Additionally, the system can be updated using the image profile and the esxcli software profile command. For details, see the vSphere Command-Line Interface Concepts and Examples and the vSphere Upgrade Guide.