Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

VMware ESX 4.1, Patch ESX410-201110201-SG: Updates the VMware ESX 4.1 Core and CIM components (2002303)

Details

Product Version
ESX 4.1 Update 2.
Patch Classification
Security
Build Information
For build information, see KB 2002337.
Host Reboot Required
Yes
Virtual Machine Migration or Shutdown Required
Yes
PRs Fixed
519340, 520171, 530465, 554760, 558172, 560762, 566841, 575993, 587921, 603039, 603608, 607645, 608251, 610356, 616028, 616065, 616093, 617080, 618011, 620006, 620635, 621306, 621957, 626601, 629880, 631253, 633333, 633355, 634841, 636361, 636705, 636709, 637037, 638321, 640008, 642081, 649281, 649413, 650463, 652013, 652054, 652236, 652658, 652831, 653369, 653808, 655453, 658757, 659236, 660442, 662589, 663584, 671017, 672997, 673643, 676116, 676894, 679055, 679113, 679789, 680409, 681229, 681986, 684040, 687278, 687402, 689196, 692220, 694569, 695510, 697483, 698298, 698414, 700664, 702364, 704605, 706872, 710560, 711794, 714213, 715469, 719776, 724146, 726599, 728132, 736703, 744361, 747603, 750983
Affected Hardware
SGI InfiniteStorage 4000, SGI InfiniteStorage 4100, SGI InfiniteStorage 4600, VMXNET3 NIC
Affected Software
esxtop and resxtop, Snapshot Manager, wsman, Small-Footprint CIM Broker daemon, LSI storelib library, vmkiscsi-tool utility, VMW_SATP_ALUA plug-ins, SVGA driver, VMware Tools, Microsoft SQL Server, Network Driver Interface Specification
VIBs Included
  • vmware-esx-apps
  • kernel
  • omc
  • openldap
  • openldap-clients
  • passwd
  • vmware-esx-backuptools
  • vmware-esx-cim
  • vmware-esx-docs
  • vmware-esx-drivers-scsi-mptspi
  • vmware-esx-drivers-vmklinux-vmklinux
  • vmware-esx-esxcli
  • vmware-esx-guest-install
  • vmware-esx-ima-qla4xxx
  • 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-lnxcfg
  • vmware-esx-lsi
  • vmware-esx-microcode
  • vmware-esx-nmp
  • vmware-esx-pam-config
  • vmware-esx-pam-krb5
  • vmware-esx-pam-krb5-64
  • vmware-esx-perftools
  • vmware-esx-scripts
  • vmware-esx-srvrmgmt
  • vmware-esx-tools
  • vmware-esx-uwlibs
  • vmware-esx-vmkctl
  • vmware-esx-vmkernel64
  • vmware-esx-vmnixmod
  • vmware-esx-vmware-release-4
  • vmware-esx-vmwauth
  • vmware-esx-vmx
  • vmware-hostd-esx
  • vmwprovider
Related CVE numbers
CVE-2010-0211, CVE-2010-0212, CVE-2010-2054, CVE-2010-1083, CVE-2010-2492, CVE-2010-2798, CVE-2010-2938, CVE-2010-2942, CVE-2010-2943, CVE-2010-3015, CVE-2010-3904, CVE-2010-3066, CVE-2010-3067, CVE-2010-3078, CVE-2010-3086, CVE-2010-3477, CVE-2010-3432, CVE-2010-3442, CVE-2010-3699, CVE-2010-3858, CVE-2010-3859, CVE-2010-3865, CVE-2010-3876, CVE-2010-3880, CVE-2010-4083, CVE-2010-4157, CVE-2010-4161, CVE-2010-4242, CVE-2010-4247, CVE-2010-4248, CVE-2010-3296, CVE-2010-3877, CVE-2010-4072, CVE-2010-4073, CVE-2010-4075, CVE-2010-4080, CVE-2010-4081, CVE-2010-4158, CVE-2010-4243, CVE-2010-4255, CVE-2010-4263, CVE-2010-4343, CVE-2010-4526, CVE-2010-4249, CVE-2010-4251, CVE-2010-4655, CVE-2010-4346, CVE-2011-0521, CVE-2011-0710, CVE-2011-1010, CVE-2011-1090, CVE-2011-1478, CVE-2010-0296, CVE-2011-0536, CVE-2011-1071, CVE-2011-1095, CVE-2011-1658, CVE-2011-1659, CVE-2011-1494 and CVE-2011-1495

Solution

This patch resolves the following issues:

  • 519340: Attempts to remove a vNetwork Distributed Switch from the configuration section results in the following error message

    Call "HostNetworkSystem.UpdateNetworkConfig" for object "networkSystem-3739" on vCenter Server "loganvc29.eng.vmware.com" failed.

    Operation failed, diagnostics report: DVS DvsPortset-0 has 1 shadow or zombie port.


  • 520171: When you browse ESX 3.5/4.0 host through Managed Object Browser (MOB), (Content > ha-folder-root > ha-datacenter > ha-folder-vm > Click particular VM value -> summary -> config) instead of connecting it to vCenter server, then the CPU reservation value [virtualMachineConfigSummary.cpuReservation] and memory reservation value [virtualMachineConfigSummary.memoryReservation] for the virtual machines is displayed as "unset".

  • 530465: When you disconnect a storage cable from ESX 4.0, browse to the datastore created on this FC SAN using MOB (Managed Object Browser) and invoke the RefreshDatastore method on the MoRef (Managed Object Reference) of the defunct datastore. The RefreshDatastore API does not display any error.

  • 554760: When you upgrade an ESX host from ESX 4.0 to ESX 4.0 update 1, only one port of the serial card works eventhough all the ports on the serial card were working fine before the upgrade. When you power-on the virtual machine, on the console you might see the following error message:

    "serial0: The "/dev/ttyS1" file does not appear to be a serial port: Input/output error. Virtual device serial0 will start disconnected."

  • 558172: When you perform vMotion on multiple virtual machines present on two ESX hosts, the memory on one ESX host gets overcommitted and the page allocation fails. This results in a log spew with the following warning:
    WARNING: vmklinux26: AllocPages: gfp_mask=0xd4, order=0x0, vmk_PktSlabAllocPage returned 'Out of memory' in the vmkernel log during vMotion

  • 560762: After installing OEM provider VIBs, vCenter Server provides only one ProviderEnabled configuration item (/UserVars/CIMoemProviderEnabled) to turn on/off all the OEM provider VIBs that you have installed. Now if you install OEM provider VIBs, /UserVars/CIMoem- ProviderEnabled configuration items are created for each VIB. You can enable/disable each provider separately.

  • 566841: Attempts to install VMware Tools on a virtual machine with Windows NT 4.0 operating system succeeds. However, the vSphere Client displays the tools status as VMware Tools: Out of date. A new method is used to check for the tools version, this resolves the issue.

  • 575993: If the number of CPU cores per socket in a physical machine increases, ESX host takes more time to complete the following tasks:
    • Boot the host machine.
    • Adding host to a HA cluster.
    • Collecting vm-support diagnostic data.
    For more information, see KB 2006081.

  • 587921: When you upgrade VMware Tool the upgrade might fail because, some Linux distributions periodically delete old files and folders in /tmp.

  • 603039: If you check the Hardware Status of an ESX/ HP DL980 G7 connected through vCenter 4.1, the Memory type is displayed as Unknown. This happens because, the Common Interface Model (CIM) does not support DDR3 (DMBF 0x18 type) memory type.

  • 603608: If you do not configure SWiSCSI using Broadcom dependent adapter and upgrade ESX from 4.0 to 4.1, ESX host fails to detect the iSCSI capabilities of NC382i adapter.

  • 607645: The customization of the hot clone of a Windows 2008 R2 guest operating system fails with the "auto check not found" error message, and the virtual machine reboots continuously.

  • 608251: Windows virtual machine loses network connectivity after upgrading VMware Tools.

  • 610356: Memory Hotplug is not a supported feature on SLES 11 32-bit guest operating systems. The Memory/CPU Hotplug option at Edit Settings > Options is disabled in this release.

  • 616028: After you upgrade ESX from 3.5 to 4.1, the CPU utilization in Netware 5.1 Service Pack 8 virtual machine increases by more than 50 percent. Changing the default mode for Netware virtual machines resolves the issue.

  • 616065: On a Windows 2008 R2 virtual machine, when you add a dynamic disk and take a quiesced snapshot, disk manager displays a failed disk or missing disk message. This issue is applicable for the following Windows operating systems.
    • Windows 2003
    • Windows Vista
    • Windows 2008
    • Windows 7


  • 616093: Issues with filter_deserialzation and ws_deserialize_duration functions related to Openwsman.

  • 617080: The openldap and openldap-client RPMs are updated to 2.3.43-12.el5_5.1 version. This resolves multiple security issues with the OpenLDAP libraries. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2010-0211 and CVE-2010-0212 to these issues.

  • 618011: In vSphere 4.1 client, if you select the Restart Guest option for a symmetric multiprocessing virtual machine with Windows 2003 Service Pack 2 R2 running on uniprocessor kernel, the virtual machine fails and displays a blue screen after boot up at the end.

  • 620006: In vCenter, a cloned Windows 2000 Professional virtual machine displays Windows 2000 as the guest operating system in the vmx file instead of Windows 2000 Professional.

  • 620635: The Windows HGFS provider Dll results in a deadlock for applications such as eEye Retina due to incorrect provider implementation of Windows WNetAddConnection2 or WNetCancelConnection APIs in a multi-threaded environment.

  • 621306: Certain Linux virtual machines such as SLES 10 SP2 configured with the clock=pit parameter might fail to boot. This issue is known to occur when you use hardware virtualization on Intel systems.

  • 621957: When you perform concurrent vmotions or put a 4.1 host in maintenance mode which is a part of DRS enabled cluster using vCenter 4.1 or vSphere 4.1, then evacuation of virtual machines fails with the following error messages

    Migration to host <> failed with error Out of memory (195887124). vMotion migration [184468762:1286284186972455] write function failed.

  • 626601: On ESX hosts, log messages in excess of about 2048 bytes might not be written to /var/log/messages.

  • 629880: This release resolves an integer overflow issue in the SFCB that arises when the httpMaxContentLength is changed from its default value to 0 in in /etc/sfcb/sfcb.cfg. The integer overflow could allow remote attackers to cause a denial of service (heap memory corruption) or possibly execute arbitrary code via a large integer in the Content-Length HTTP header. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2010-2054 to this issue.

  • 631253: The Vsphere Client Health Status shows incorrect voltages and temperatures on the new Nehalem-EX based server due to IPMI driver timeout. You can change the default value in IPMI driver using the following commands:
    esxcfg-advcfg -A CIMOemIpmiRetries --add-desc 'oem ipmi retries' --add-default 4 --add-type int --add-min 0 --add-max 100
    esxcfg-advcfg -A CIMOemIpmiRetryTime --add-desc 'oem ipmi retry time' --add-default 1000 --add-type int --add-min 0 --add-max 10000/etc/init.d/sfcbd-watchdog restart

  • 633333: The Datastore browser is not able to manage symlinks on NFS volumes when connected through vSphere Client 4.1.

  • 633355: In Windows guest operating systems, when you upgrade ESX 3.5 to ESX 4.1 and the hardware version from 4 to 7, the device status for NIC is displayed as:

    "This hardware device is not connected to the computer (Code 45)".
    Uninstalling and reinstalling the NIC solves the issue.

  • 634841: When you try to install VMware Tools on an RHEL 2.1 virtual machine running on ESX 4.1 by running the vmware-install.pl script, the install process fails with the following error message

    Creating a new initrd boot image for the kernel. Error opening /tmp/vmware-fonts2/system_fonts.conf Execution aborted.

  • 636361: In ESX 4.x, the maxSample performance statistic property in PerfQuerySpec displays incorrect.

  • 636705: ESX host fails with a purple diagnostic screen when you run 'less /proc/scsi/*/*' from service console.

  • 636709: Configuration file entries were overwritten on Linux virtual machines while installing VMware Tools.

  • 637037: Disabled CUPS (Common UNIX Printing System) service starts automatically, when VMware Tools is installed or upgraded on SUSE Linux Enterprise Server 10 Service Pack 3, x86 virtual machine. Disable the CUPS service in SUSE Linux Enterprise 10 and Red Hat Enterprise Linux 5 using the following commands:
    On SUSE Linux Enterprise 10:
    Run
    chkconfig --level 2345 cups off and chkconfig --level 2345 cupsrenice off
    and disable the CUPS service.
    Check the service status using the command
    service cups status
    chkconfig -l|grep -i cups
    make sure that the service is disabled.

    On Red Hat Enterprise Linux 5:
    Run
    chkconfig --level 2345 cups off and system-config-services.

  • 638321: When you attach a MAI KEYLOK II USB device to an ESX host on CentOS 5.5 or RHEL 5.4 or Ubuntu 9.10 or Ubuntu10.04 operating systems, the Linux virtual machines present in the guest operating system cannot access it. The device is visible in the guest operating system, but the Linux virtual machines cannot use it.

  • 640008: When you perform cold migration between two ESX 4.1 hosts present on two different clusters, the migration fails.

  • 642081: When viewing multipath information from the Vmware Infrastructure Client connected to ESX host or vCenter Server, you might not see the target information for some paths of working LUNs.

    Replacing the empty values for port numbers with the new path info this resolves the issue.

  • 649281: In ESX, virtual machines cannot view the raw device mapping files that resides on Dell MD36xxi storage array.

  • 649413: The ESX host does not consider the memory reservation while calculating the provisioned space for a powered-off virtual machine. As a result, the vSphere Client might display a discrepancy in the values for provisioned space while the virtual machine is powered-on or powered-off.

  • 650463: The vSphere client does not display an alert message if Syslog is not configured.

  • 652013: Snapshots of upgraded VMFS volumes fail to mount on ESX 4.x hosts.


  • 652054: If a peer of a VMCI stream socket connection (for example, stream socket server running in a server virtual machine) detaches from a queue pair while the connection state is connecting, then the other peer (for example, stream socket client with a blocking connect) might fail to connect.
    The release ESX 4.1 Update 2 treats the peer detach as a reset and propagates the following error message to the other peer:

    Connection reset by peer

  • 652236: A vMotion operation might fail with error messages indicating locked swap files in workingdir directory under NAS datastore.

  • 652658: The first packet that e1000 vNIC sends has an invalid MAC address.

  • 652831: vMotion intermittently fails with a timeout message.

  • 653369: Kerberos user authentication fails on certain ESX hosts. This issue occurs in environments where only the UDP 88 port is enabled for Kerberos.

  • 653808: When you install VMware Tools and switch between kernels, vsock and vmmemctl modules are not loaded at boot. The following error message appears when you run a dmesg command or when you try to manually load the modules for the wrong kernel:

    vmmemctl: disagrees about version of symbol module_layout

    vsock: disagrees about version of symbol module_layout

  • 655453: While performing snapshot operations, if you simultaneously perform another task such as browsing a datastore, the virtual machine might be abruptly powered off. Error messages similar to the following are written to vmware.log:

    vmx| [msg.disk.configureDiskError] Reason: Failed to lock the file

    vmx| Msg_Post: Error

    vmx| [msg.checkpoint.continuesync.fail] Error encountered while restarting virtual machine after taking snapshot. The virtual machine will be powered off.


  • 658757: When one controller takes over another controller, the datastores that reside on LUNs of the taken over controller might become inactive.

  • 659236: VMware Tools service (vmtoolsd.exe) fails on 64 bit Windows virtual machines when the virtual memory allocation order is forced from top to down using a registry key. In Windows, VirtualAlloc can be forced to allocate memory from top to down using the AllocationPreference registry key as mentioned in the following link: http://www.microsoft.com/whdc/system/platform/server/PAE (/PAEdrv.mspx).

  • 660442: Memory imbalance warning for ESX hosts between NUMA nodes.

  • 662589: For devices using Native Multipathing Plug-in's (NMP) round robin path selection policy, if you set the value of the useANO setting to TRUE, it is reset to FALSE after a system reboot.

  • 663584: ESX host configured with vNetwork Distributed Switch (vDS) disconnects from the vCenter Server and does not reconnect even after multiple attempts.

  • 671017: If you remove a virtual machine snapshot, the VMware hostd management agent might fail and display a backtrace similar to the following:

    [2010-02-23 09:26:36.463 F6525B90 error 'App']

    Exception: Assert Failed: "_config != __null && _view != __null" @ bora/vim/hostd/vmsvc/vmSnapshot.cpp:1494


  • 672997: The objects shared between task and internationalization filter results in the frequent failure of hostd process.

  • 673643: After you create, power-on, and delete a virtual machine, statistics such as CPU and memory usage of that virtual machine displayed in the vSphere Client performance chart might be invalid.

  • 676116: VMware Tools service (vmtoolsd) might fail after you install VMware Tools on a Linux guest with operating system name greater than 100 characters.

    For more information, see KB 1034633.

  • 676894: VMware hosted service might fail during a quiesced snapshot operation.

  • 679055: Network connectivity might fail when VLANs are configured with physical NICs using be2net or ixgbe drivers.

  • 679113: Cannot log in to the ESX 4.1 host using non-local user credentials.

  • 679789: ESX host stops responding when SNMP queries are sent using a MIB file.

  • 680409: ESX 4.1 installation fails on Hitachi BS320 AC51A3 blade server with LSI SAS Mezzanine controller (LSI 1064E) .

  • 681229: Modifying snapshots using the commands vim-cmd vmsvc/snapshot.remove or vim-cmd vmsvc/snapshot.revert fails when applied against certain snapshot tree structures. You can get the snapshotId by running the command vim-cmd vmsvc/snapshot.get .
    You can use the following new syntax when working with the same commands:
    • Revert to snapshot: vim-cmd vmsvc/snapshot.revert [suppressPowerOff/suppressPowerOn]
    • Remove a snapshot: vim-cmd vmsvc/snapshot.remove
  • 681986: Virtual machines with large RAM looses ping during vmotion.

  • 684040: DHCP server runs out of IP addresses.

  • 687278: X11 configuration is changed after installing VMware Tools.

  • 687402: When multiple users try to login or logout of a virtual machine at the same time, the VMwareUser.exe process may crash. This causes copy/paste to fail.

  • 689196: CIM server sends invalid alerts to IBM Systems Director.
    The CIM server (sfcbd) process on the ESX host might send invalid OMC_IpmiAlertIndication alerts related to missing CPUs to IBM Systems Director software. This issue has been observed on IBM blade servers such as IBM LS22 7901-AC1.

  • 692220: NUMA imbalance after vMotion of virtual machines. See KB 2000740 for more information.

  • 694569: A Virtual Machine running on snapshots can become unresponsive if the "Limit IOPS" value for the virtual disk is changed.

  • 695510: Virtual machine configured with fixed passthrough device fails to power on.

  • 695847: The openldap Service Console RPMs are updated to version 2.3.43-12.el5_6.7 for the latest bug fixes.


  • 697483: The Machine Check Exception purple diagnostic screen did not guide users in case of certain hardware issues


  • 698298: An ESX host might fail with a purple diagnostic screen that displays an error message similar to the following: #0 Panic (fmt=0x41800c703488 "PANIC %s:%d - Usage error in dlmalloc")
    You might see this error in the UserEventfdClose path of the backtrace information.

  • 698414: The Windows virtual machine with VMware Tools reports Event ID 105 in the Event Viewer tab. See KB 1037755 for more information.

  • 700664: vSphere Client does not display the serial tag of ESX hosts based on certain platforms.

  • 702364: Some HP Servers on ESX 4.1 hosts with the Automatic Power On option disabled in BIOS automatically power on when you connect the power cable.

  • 704605: Unable to add a USB device to a virtual machine. For more information see KB 1039359..

  • 706872: IPMI logs in ESX 4.x consume excessive disk space after a BMC reset or firmware update.

  • 710560: This patch updates the ESX Service Console Operating System (COS) kernel to kernel-2.6.18-238.9.1.el5 and fixes multiple security issues in the COS kernel. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2010-1083, CVE-2010-2492, CVE-2010-2798, CVE-2010-2938, CVE-2010-2942, CVE-2010-2943, CVE-2010-3015, CVE-2010-3904, CVE-2010-3066, CVE-2010-3067, CVE-2010-3078, CVE-2010-3086, CVE-2010-3477, CVE-2010-3432, CVE-2010-3442, CVE-2010-3699, CVE-2010-3858, CVE-2010-3859, CVE-2010-3865, CVE-2010-3876, CVE-2010-3880, CVE-2010-4083, CVE-2010-4157, CVE-2010-4161, CVE-2010-4242, CVE-2010-4247, CVE-2010-4248, CVE-2010-3296, CVE-2010-3877, CVE-2010-4072, CVE-2010-4073, CVE-2010-4075, CVE-2010-4080, CVE-2010-4081, CVE-2010-4158, CVE-2010-4243, CVE-2010-4255, CVE-2010-4263, CVE-2010-4343, CVE-2010-4526, CVE-2010-4249, CVE-2010-4251, CVE-2010-4655, CVE-2010-4346, CVE-2011-0521, CVE-2011-0710, CVE-2011-1010, CVE-2011-1090, and CVE-2011-1478 to these issues.

  • 711794: VMware Tools installation fails to complete on Solaris 10 64 bit virtual machines. Attempts to start the VMware Tools service by running the VMware Tools configuration script (vmware-config-tools.pl) fail with an error message similar to the following:
    Guest operating system daemon:Killed
    Unable to start services for VMware Tools
    Execution aborted.
    Attempts to start the VMware Tools daemon from command line fail with an error message similar to the following: ld.so.1: vmtoolsd: fatal: libvmtools.so: open failed: No such file or directory

  • 714213: The esxtop tool displays abnormal values in its memory view.

  • 715469: CPU shares are not enforced in an under-committed ESX host.

  • 719776: The glibc third-party library is updated to 2.5-58.el5_6.2 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 address these issues.

  • 724146: Virtual machines on a vNetwork Distributed Switch (vDS) configured with VLANs might lose network connectivity upon boot if you configure Private VLANs on the vDS. However, disconnecting and reconnecting the up-link solves the problem.
    This issue has been observed on be2net NICs and ixgbe vNICs.

  • 726599: Mouse movements might cause SVGA messages to be repeatedly written to vmware.log.
    The I/O generated by this repeated logging might generate increased load on storage systems.

  • 728132: Purple diagnostic screen with vShield or third-party vSphere integrated firewall products. See KB 2004893 for more information.

  • 736703: Upgrade from ESX 4.0.x to ESX 4.1 using VMware Update Manager fails on IBM x3650 M2 servers.

  • 744361: The settings that disable the "Managed Object Browser" and "ESX Welcome page" are lost after installing patch ESX410-201104001 on an ESX 4.1 U1 host.

  • 747603: Virtual machine might not power on after failover in an HA cluster.

  • 750983: The mptsas, mpt2sas, and mptspi drivers are updated, which resolves multiple security issues in the mpt2sas driver, including possible local privilege escalation. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2011-1494 and CVE-2011-1495 to these issues.

    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.

    Feedback

    • 6 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)
    • 6 Ratings
    Actions
    KB: