Search the VMware Knowledge Base (KB)
View by Article ID

VMware ESX 4.1, Patch Release ESX410-201304401-SG: Updates VMkernel, CIM, Tools, and others (2045251)

  • 0 Ratings


Product Version
ESX 4.1
Patch Classification
See KB 2014447 if using Update Manager 5.0
Build Information
For build information, see KB 2045257.
Host Reboot Required
Virtual Machine Migration or Shutdown Required
PRs Fixed
725865, 825330, 853322, 858354, 877569, 919381, 929736, 938382, 947512, 951770, 959171, 967745, 969138, 974898, 983325, 987080, 999839, 965715
Affected Hardware
Affected Software
VIBs Included
  • vmware-esx-apps
  • vmware-esx-cim
  • vmware-esx-iscsi
  • vmware-esx-likewise-ad-provider
  • vmware-esx-likewise-krb5
  • vmware-esx-likewise-krb5-64
  • vmware-esx-likewise-krb5-workstation
  • vmware-esx-likewise-open
  • vmware-esx-likewise-open-64
  • vmware-esx-likewise-openldap
  • vmware-esx-likewise-openldap-64
  • vmware-esx-pam-config
  • vmware-esx-pam-krb5
  • vmware-esx-pam-krb5-64
  • vmware-esx-scripts
  • vmware-esx-srvrmgmt
  • vmware-esx-tools
  • vmware-esx-vmkctl
  • vmware-esx-vmkernel64
  • vmware-esx-vmnixmod
  • vmware-esx-vmwauth
  • vmware-esx-vmx
  • vmware-hostd-esx
  • vmwprovider
  • Related CVE numbers


    Summaries and Symptoms

    This patch resolves the following issues:

    • When you copy a file that is 1GB or more from a virtual machine to FAT 32 USB drive, the data transfer might not be successful.
      Also, while copying these large files, sometimes the MD5 checksum of the source file does not match that of the destination file on the USB mass storage device.

    • When you set an ESX host, on which IPv6 support is disabled, to use Active Directory authentication, the packet capture might still contain AAAA records for DNS queries.

    • When multiple VLANs are configured for a network interface in Linux guest operating systems, VMware Tools might have insufficient memory.

    • When a SCSI Request Sense command is sent to Raw Device Mapping (RDM) in Physical Mode from a guest operating system, sometimes the returned sense data is NULL (zeroed).

    • The iSCSI initiator login timeout value when updated through Advanced Setting in VirtualCenter for software iSCSI and dependent iSCSI adapters might not get inherited for the discovery phase.

    • When you perform certain virtual machine operations, an issue related to metadata corruption of LUNs might sometimes cause an ESX host to fail with a purple screen and display error messages similar to the following:
      @BlueScreen: #DE Exception 0 in world 4277:helper23-15 @ 0x41801edccb6e3:21:13:31.624 cpu7:4277)Code start: 0x41801e600000 VMK uptime: 3:21:13:31.6243:21:13:31.625 cpu7:4277)0x417f805afed0:[0x41801edccb6e]Fil3_DirIoctl@esx:nover+0x389 stack: 0x410007741f603:21:13:31.625 cpu7:4277)0x417f805aff10:[0x41801e820f99]FSS_Ioctl@vmkernel:nover+0x5c stack: 0x2001cf5303:21:13:31.625 cpu7:4277)0x417f805aff90:[0x41801e6dcf03]HostFileIoctlFn@vmkernel:nover+0xe2 stack: 0x417f805afff03:21:13:31.625 cpu7:4277)0x417f805afff0:[0x41801e629a5a]helpFunc@vmkernel:nover+0x501 stack: 0x03:21:13:31.626 cpu7:4277)0x417f805afff8:[0x0] stack: 0x0
      Metadata corruption of LUNs results in an error message after you apply this patch.

    • When you configure Symmetric Multi-Processing (SMP) on a Red Hat Enterprise Linux 6.2 guest operating system and attempt to capture a kernel dump using the Red Hat Crash Utility kdump mechanism, the kernel dump might not be created using kdump.
      This issue occurs with multi-vCPU virtual machines and when more than one virtual socket is used on VMware Paravirtual SCSI Controller.

    • While performing a Network File Copy (NFC) across the WAN, you might encounter TCP performance-related issues on Long Fat Network (LFN) links.

    • All consequent Common Information Model (CIM) queries within the same CIM connection might fail after enumerating instances of CIM_RegisteredProfile from root/pg_interop namespace.

    • If a third-party module creates a custom SCSI command structure using VMKernel APIs and issues this SCSI command structure, the ESX host might fail with a purple diagnostic screen.
      This issue occurs if the SCSI command requires a Direct Memory Access (DMA) transfer and the data direction in the SCSI command structure is left uninitialized.

    • Multiple virtual machines might fail to reboot and generate VMX core file after reboot. This issue is only seen with virtual machines that are migrated from ESX/ESXi 3.5 hosts to ESX/ESXi hosts with versions ESX/ESXi 4.0 Update 2, ESX/ESXi 4.1 Update 2, ESXi 5.0 Update 2, and above using VMotion.

    • When a virtual machine that is on a vSphere Distributed Switch (DVS) is migrated from ESXi 5.1 host to ESX 4.1 Classic, you might not be able to establish a network connection with the virtual machine.
      This issue results in the failure of dv port connection.
      This patch resolves the issue if the length of the Distributed Virtual Uplink (dvUplink) name is less than 32 characters. The limit for the dvUplink name length for ESX 4.1 Classic is 31 characters.

    • ESX hosts might fail with a purple diagnostic screen due to failure in memory allocation from world heap for firing traces, a mechanism used by VMkernel to batch up after write traces on guest pages. This issue occurs when this failure of memory allocation is not handled properly.

    • You might not be successful in enabling a High Availability (HA) cluster after a single host of the same HA cluster is placed in maintenance mode.
      This issue occurs when the value of the inode descriptor number is not set correctly in ESX root file system (VisorFS), and as a result, the stat calls on those inodes fail.

    • Netlogond might consume high memory in an Active Directory environment with multiple unreachable Domain Controllers. As a result, Netlogond might fail and ESX host might lose Active Directory functionality.

    • Virtual machines might fail when vCloud Director (vCD) or VMware Service Manager (VSM) or vCenter Lab Manager is configured to manage vCenter server or vSphere Client and the Thumbnail feature is enabled. This results in insufficient memory and subsequent failure of the virtual machine.

    • Virtual Symmetric Multi Processing (SMP) Solaris guest operating systems might stop responding while using the fast reboot mechanism of Solaris.
      This issue occurs when the SMI handler is not managed properly.

    • The VMkernel multiextent module is no longer loaded by default, to resolve a stability issue. However, this might cause virtual machines with 2GB sparse virtual machine disk (VMDK) file format not to power on. You must load the VMkernel multiextent module manually by running the following commands:

      • To load the VMkernel multiextent module:
        # esxcfg-module multiextent
      • To unload the VMkernel multiextent module:
        # esxcfg-module –u multiextent

      Deployment Considerations

      None beyond the required patch bundles and reboot information listed in the table above.

      Patch Download and Installation

      See the VMware vCenter Update Manager Administration Guide for instructions about using Update Manager to download and install patches to automatically update ESX 4.1 hosts.

      To update ESX 4.1 hosts without using Update Manager, download the patch ZIP file from and install the bulletin by using esxupdate from the command line of the host. For more information, see the ESX 4.1 Patch Management Guide.

      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.


      • 0 Ratings

      Did this article help you?
      This article resolved my issue.
      This article did not resolve my issue.
      This article helped but additional information was required to resolve my issue.

      What can we do to improve this information? (4000 or fewer characters)

      Please enter the Captcha code before clicking Submit.
      • 0 Ratings