VMware ESXi 5.0 Patch Image Profile ESXi-5.0.0-20111204001-standard
search cancel

VMware ESXi 5.0 Patch Image Profile ESXi-5.0.0-20111204001-standard


Article ID: 334314


Updated On:


VMware vSphere ESXi


Release date: December 15, 2011

Profile Name ESXi-5.0.0-20111204001-standard
BuildFor build information see KB 2007680
VendorVMware, Inc
Creation Date
October 31, 2011
Acceptance Level Partner
Affected HardwareN/A
Affected SoftwareN/A
Affected VIBs VMware:esx-base:5.0.0-0.3.515841
PRs Fixed730045, 746126, 746703, 759459, 710385, 725598, 730074, 730103, 739387, 740224, 745747, 750309, 736768, 745789 and 753484
Related CVE numbersCVE-2009-4536, CVE-2010-0296, CVE-2011-0536, CVE-2011-1071, CVE-2011-1095, CVE-2011-1658 and CVE-2011-1659


VMware vSphere ESXi 5.0


Summaries and Symptoms

This image profile updates the esx-base, tools-light, net-e1000, net-e1000e, misc-drivers, and net-be2net VIBs to resolve multiple issues.

  • The updated esx-base VIB resolves the following issues:
    • Updates the glibc third party library to resolve multiple security issues.
      The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2010-0296, CVE-2011-0536, CVE-2011-1071, CVE-2011-1095, CVE-2011-1658 and CVE-2011-1659 to these issues.

    • When vMotion or snapshot operations are performed on virtual machines, host memory might get corrupted in very rare instances.

    • When a hot spare disk that is added to a RAID group is accessed before the disk instance finishes initialization or if the disk is removed while an instance of it is being accessed, a race condition might occur causing the vSphere Client to not display information about the RAID controllers and the vSphere Client user interface might also not respond for a very long time.

    • vMotion fails with The checkpoint data length or the offset exceeds the maximum checkpoint data length error message when:
      • The resolution of the virtual machines is higher than 1280x1024, or smaller if you are using a second screen
      • The guest operating system is using the WDDM driver (Windows 7, Windows 2008 R2, Windows 2008, Windows Vista)
      • The virtual machine is using Virtual Machine Hardware version 8.

    • Creating host profiles of ESX i 5.0 hosts might fail when the host profile creation process is unable to resolve the hostname and IP address of the host by relying on the DNS for hostname and IP address lookup. An error message similar to the following is displayed:
      Call"HostProfileManager.CreateProfile" for object "HostProfileManager" on vCenter Server"<Server_Name> failed.
      Error extracting indication configuation: [Errno- 2] Name or service not known.

    • In vSphere 5.0, Thin Provisioning is enabled by default on devices that adhere to T10 standards. On such thin provisioned LUNs, vSphere issues SCSI UNMAP commands to help the storage arrays reclaim unused space. Sending UNMAP commands might cause performance issues with operations such as snapshot consolidation or storage vMotion.
      This patch resolves the issue by disabling the space reclamation feature, by default.

    • If a user subscribes for an ESXi Server’s CIM indications from more than one client (for example, c1 and c2) and deletes the subscription from the first client (c1), the other clients (C2) might fail to receive any indication notification from the host.

    • It also provides you with the option of configuring the iSCSI initiator login timeout value for software iSCSI and dependent iSCSI adapters.
      For example, to set the login timeout value to 10 seconds you can use commands similar to the following:
      • ~ # vmkiscsi-tool -W -a "login_timeout=10" vmhba37
      • ~ # esxcli iscsi adapter param set -A vmhba37 -k LoginTimeout -v 10

      The default login timeout value is 5 seconds and the maximum value that you can set is 60 seconds.
      We recommend that you change the login timeout value only if suggested by the storage vendor.

  • The updated tools-light VIB updates the pre-built kernel driver modules for Ubuntu 10.04.3, Ubuntu 11.04, and Ubuntu 11.10. In addition, it also resolves the following issues:
    • When VMware Tools installed on a Windows XP virtual machine running on an ESXi 5.0 host patched with ESXi500-201109001 is upgraded using the automatic upgrade option, a warning message similar to the following might be displayed in the Software Installation window of the virtual machine:
      The software you are installing has not passed Windows Logo testing to verify its compatibility with Windows XP.

      This issue also occurs when VMware Tools is installed by using the Install/Upgrade Tools option and selecting the complete mode, or custom mode with LSI driver selected.

    • When vShield Endpoint driver is installed using the VMware Tools installer, the Endpoint driver might fail to load (before the virtual machine is rebooted) as it is installed before the VMCI driver is installed and loaded. This issue is resolved by installing the VMCI driver before installing the Endpoint driver.

    • When a virtual machine with Windows 2003 guest operating system is installed with a Windows XP display driver model (XPDM) driver, the virtual machine might stop responding with a malloc() in vmx_fb.dll error and fails with a blue screen and STOP 8E vmx_fb.dll error.
      This VIB updates the VMware display driver version to

    • VMXNET 3 driver versions to fail to activate the device if the number of vCPUs that you assign to a virtual machine is not a power of two. You might see an error message similar to the following while running the demsg command:
      Failed to activate dev eth0:error 1

      An error message similar to the following might be written to vmware.log:
      VMXNET3 user: failed to activate Ethernet1 with status 0xbad0007

  • The updated net-e1000 and net-e1000e VIBs resolve a security issue in the e1000 and e1000e Linux drivers for Intel PRO/1000 adapters that allows a remote attacker to bypass packet filters and send manipulated packets.
    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-4536 to this issue.

  • The updated misc-drivers VIB resolves an issue where if software FCoE drivers are used with NICs that support partial FCoE offload, the ESXi host might fail to boot on Cisco's UCS rack-mount servers and stops responding with a backtrace similar to the following on the purple screen:
    #0 0x0000000000000000 in ?? ()
    #1 0x000041801763f8f9 in fcoe_ctlr_l2_link_ok (work=0x410013404eb0) at vmkdrivers/src_9/drivers/scsi/fcoe/libfcoe.c:1419
    #2 fcoe_ctlr_timer_work (work=0x410013404eb0) at vmkdrivers/src_9/drivers/scsi/fcoe/libfcoe.c:1460
    #3 0x000041801744e98d in vmklnx_workqueue_callout (data=<value optimized out>)
    at vmkdrivers/src_9/vmklinux_9/vmware/linux_workqueue.c:690
    #4 0x0000418016c611d8 in helpFunc (data=<value optimized out>) at bora/vmkernel/main/helper.c:3213
    #5 0x0000000000000000 in ?? ()

  • The updated net-be2net VIB resolves an issue where, when using vSphere 5.0 with Emulex BE2/BE3 NICs (be2net driver) in a HP FlexFabric/Flex-10 or IBM Virtual Fabric Adapter (VFA) environment, connectivity may not work properly on Windows VMs or the server when VLANs are configured.

Deployment Considerations

  • The six VIBs that are updated with this image profile are listed in the table above.

  • The VMware tools installer of 32-bit Ubuntu 11.10 might not be able to install pre-built kernel modules, so it searches for gcc and kernel headers in order to compile kernel modules. Ensure that gcc and kernel headers are installed in Ubuntu 11.10 system before installing VMware tools.
    This issue does not exist with 64-bit Ubuntu 11.10.
  • For Ubuntu 11.10 with generic-pae kernel, the Operating System Specific Package (OSP) name of VMware Tools is vmware-tools-esx-kmods-3.0.0-12.20-generic-pae.
    For example, to install VMware Tools OSP you need to use the command sudo apt-get install vmware-tools-esx-kmods-3.0.0-12.20-generic-pae.

  • When installing VMware Tools on Ubuntu 11.10 or Ubuntu 1.04, the authentication of the VMware Tools packages might fail. Enter y to proceed with the installation of the packages without authentication.

  • This image profile enables support for Mac OS X 10.7 and Mac OS X 10.7.1.
    Mac OS X 10.7.2 is not supported by this patch release.

Patch Download and Installation

An ESXi system can be updated using the image profile, by using the esxcli software profile command. For details, see the vSphere Command-Line Interface Concepts and Examples and the vSphere Upgrade Guide.

For information about image profiles and how it applies to ESXi 5.0 hosts, see Image Profiles of ESXi 5.0 Hosts (KB 2009231).

ESXi hosts can also 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.