The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
VMware ESXi 5.0, Patch ESXi500-201212203-UG: Updates VMware ESXi 5.0 tools-light vib (2033755)
Release Date: December 20, 2012
|Patch Category||Bug Fix|
|Build||For build information, see KB 2033751.|
|Host Reboot Required||No|
|Virtual Machine Migration or Shutdown Required||No|
|PRs Fixed||830393, 836693, 837005, 837008, 854919, 858969, 871622, 877459, 880758, 885149, 887575, 889366, 891703, 902238, 907080, 908279, 920615, 921398, 921804, 927965|
|Related CVE numbers||N/A|
For more information on patch and update classification, see KB 2014447.
Summaries and Symptoms
This patch updates the tools-light VIB to resolve the following issues:
- PR 858969: On guest operating systems that are not configured with a IPV4 address, the IPv6 addresses might not be displayed in the vSphere Client and also when you use the vmware-vim-cmd command.
- PR 830393: VMware Tools might not install any graphics driver on a Windows 2008 R2 operating system, so the virtual machine uses the default VESA driver. This causes performance issues in some hardware devices of the guest operating system. With this patch VMware Tools installs the WDDM driver by default, to improve performance.
- PR 836693: IP virtualization, which allows you to allocate unique IP addresses to RDP sessions might not work on a Windows Server 2008 R2 64-bit running on vSphere 4.0 Update 1. However, IP virtualization works when you configure Remote Desktop Services on a physical Windows Server 2008 R2 machine, or when you run a Windows Server 2008 R2 virtual machine on XenServer 5.5 Update 2 Dell OEM Edition.
This issue might occur if you install VMware Tools after installing Remote Desktop services.
- PR 837005: Large number of UDP packets are dropped when you use the VMXNET3 adapter with a Linux guest operating system installed on an ESXi 5.0 host.
- PR 837008: RHEL 6 virtual machine configured with Raw Device Mapping (RDM) devices through Paravirtualized SCSI (PVSCSI) adapter might encounter I/O failure after bus reset on an ESXi 5.0 host. During reset, the PVSCSI adapter causes the I/O to fail instead of executing the retry command.
- PR 838575: The network scheduler uses a single queue to allocate bandwidth between all virtual machines sharing the same network resource pool. If multiple virtual machines send network data at the same time, the available bandwidth might get exhausted before it is allocated proportionally to all virtual machines.
The improvised algorithm now uses a time based scheduling scheme to optimally allocate bandwidth to all virtual machines sharing the same network resource pool.
- PR 854919: Network connectivity to guest operating systems using kernel versions 2.6.34 or higher, and configured to use IPv6 might not work after you install VMware Tools.
- PR 877459: The VMware Tools service (vmtoolsd.exe) might fail with a VMware Tools unrecoverable error stack due to a NULL pointer error.
- PR 880758: When you upgrade VMware Tools from an earlier version to a later version, IP virtualization fails. This happens because, the ESXi host fails to check for the new VMCI driver version and is unable install the vsock DLL files.
- PR 885149: On ESXi 5.0 hosts, if more than 16 VLAN interfaces are created for a virtual machine, VMware tools might stop responding.
- PR 887575: When you install or upgrade VMware tools available with ESXi 5.0 and ESXi 5.0 Update 1 on Solaris virtual machines, the MTU size might automatically change to 9000. Even if the MTU size is changed, it reverts to 9000 when you reboot the guest operating system.
- PR 889366: After you complete installing or upgrading VMware Tools on a virtual machine, an error message similar to either of the following might be displayed:
There is no disk in the drive
No disk: exception Processing Message c0000013
- PR 891703: If you attempt to access the internet through NAT server on Windows 2008 R2 operating system with two virtual VMXNET 3 network adapters on ESXi, the NAT server might not work.
- PR 902238: The virtual machine fails during a specific backup scenario involving quiesced snapshot, this happens because the synchronous manifest file copy operation fails due to an inconsistency in callback process and forces the system to enter an invalid state.
- PR 907080: The commands setup.exe /S /v"/qn REBOOT=R" or setup.exe /S /v"/qn REBOOTPROMPT=S" suppresses the reboot of virtual machines after installation of VMware Tools. On ESXi 5.0 hosts, installation of VMware Tools installs Visual C++ runtime, even if it is already installed. This leads to a repair of the Visual C++ runtime and necessitates a reboot of the virtual machine if the command to suppress reboot is used. This is specific to Windows XP & Windows 2003 or earlier versions.
- PR 908279: When VMware tools is installed on virtual machine such as SUSE Linux Enterprise Server 11 SP1, the file permission attribute of /etc/fstab might change from 644 to 600.
- PR 921804: On Windows 2003 operating system, when the user attempts a Vmware tools upgrade the static IP settings of E1000 are lost and the guest network adapter is set to DHCP. This happens after the user uninstalls the VMware Tools from Add or Remove Programs option.
None beyond the required patch bundles and reboot information listed in the table above.
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.
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.