Kunnskapsbase

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 ESXi 3.5/4.0 host through Managed Object Browser (MOB), (Content > ha-folder-root > ha-datacenter > ha-folder-vm > Click particular virtual machine 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 ESXi 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.
  
  
• 547964: FalconStor failover results in APD (All Paths Down) state, when using QLogic QME2472 Host Bus Adapters (HBA) with ESXi 4.0.
  
  
• 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, ESXi 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 ESXi/ 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 ESXi from 4.0 to 4.1, ESXi host fails to detect the iSCSI capabilities of NC382i adapter.
  
  
• 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.
  
  
• 615430: The path status of the logical units (LUNs) connected to ESXi host is not updated, even after they are reconnected to the ESXi host. 
  
  
• 616028: After you upgrade ESXi 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.
  
  
• 616093: Issues with filter_deserialzation and ws_deserialize_duration functions related to Openwsman.
  
  
• 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.
  
  
• 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.
  
  
• 622764: Syslog service does not start if it is configured to log to a remote host that cannot be resolved through DNS when the syslogd daemon is started. This causes remote as well as local logging processes to fail.
  
  
• 626601: On ESXi 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 /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 symbolic links on NFS volumes when connected through vSphere Client 4.1.
  
  
• 634140: ESXi host connected through an Adaptec card with AIC79xx driver might fail with a purple diagnostic screen.
  
  
• 634240: When you enforce Qlogic ISP2532 HBA to work in 4GB mode and reboot the Fibre Channel switch, the link status of the Fibre Channel switch is not restored. 
  
  
• 636361: In ESXi 4.x, the maxSample performance statistic property in PerfQuerySpec displays incorrect value.
  
  
• 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.
  
  
• 640579: The megaraid_sas driver has been upgraded from 4.0.14.1-18 to 5.30. The upgrade resolves the iMR chip and gen2 chip issues. 
  
  
• 641742: The Syslog server is unable to automatically process the vpxa Syslog messages as the messages are split into multiple lines.
  
  
• 642081: The target information for fibre channel logical units of some hardware (3par array) connected to ESXi host, might not be displayed in the vSphere user interface.
  
  
• 649281: In ESXi, virtual machines cannot view the raw device mapping files that resides on Dell MD36xxi storage array.
  
  
• 649413: The ESXi 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 ESXi 4.x hosts.
  
  
• 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.
  
  
• 652732: The hostd and vpxa log messages are duplicated on /var/log/messages.
  
  
• 652831: vMotion intermittently fails with a timeout message.
  
  
• 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.
  
  
• 658173: ESXi hosts with QLogic fibre channel in-box driver fails with a purple diagnostic screen when scanning for LUNs.
  
  
• 658757: When one controller takes over another controller, the datastores that reside on LUNs of the taken over controller might become inactive.
  
  
• 660442: Memory imbalance warning for ESXi 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: ESXi host configured with vNetwork Distributed Switch (vDS) disconnects from the vCenter Server and multiple attempts to reconnect the host fail.
  
  
• 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.
  
  
• 676894: VMware hosted service might fail during a quiesced snapshot operation.
  
  
• 676932: ESXi 4.1 continuously logs SATA internal error messages to /var/log/messages file on a Dell PowerEdge system.
  
  
• 679055: Network connectivity might fail when VLANs are configured with physical NICs using be2net or ixgbe drivers.
  
  
• 679113: Cannot log in to the ESXi 4.1 host using NIS authentication.
  
  
• 679789: ESXi host stops responding when SNMP queries are sent using a MIB file .
  
  
• 680409: ESXi 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.
  
  
• 684069: The igb driver version is upgraded to 2.1.11.1.<
  
  
• 684100: The tg3 driver version is upgraded to 3.110h.v41.1. 
  
  
• 685419: The ESX host might fail with a purple diagnostic screen due to an issue with the NetXen adapter.
  
  
• 689196: CIM server sends invalid alerts to IBM Systems Director.
  
  
• 690396: An ESX host connected to a tape drive accessed using the aic79xx driver might fail with a purple screen and display an error message similar to the following when the driver tries to access a freed memory area: 
  Loop 1 frame=0x4100c059f950 ip=0x418030a936d9 cr2=0x0 cr3=0x400b9000
  
  
• 692086: When you enable Remote Tech Support Mode (SSH) or Local Tech Support Mode a warning message similar to the following is displayed in vCenter Server:
  Configuration Issues
  The Local Tech Support Mode for the host localhost.localdomain has been enabled.
  Remote Tech Support Mode(SSH) for the host has been enabled
  Now you can disable this warning by setting the UserVars.SuppressShellWarning parameter in vCenter Server.
  
  
• 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: A Virtual machine configured with fixed passthrough device fails to power on.
  
  
• 695847: The third-party openldap libraries are updated to version 2.3.43-12.el5_6.7 for the latest bug fixes.
  
  
• 697483: The Machine Check Exception purple diagnostic screen does 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. 
  
  
• 700664: vSphere Client does not display the service tag of ESXi hosts based on certain platforms.
  
  
• 702364: Some HP Servers on ESXi 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.
  
  
• 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 userworld glibc third-party library is updated to 2.5-58.el5_6.2 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. 
  
  
• 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 had 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.
  
  
• 730196: The third-party mpt2sas driver has been updated.
  
  
• 735269: Intel e1000 and e1000e drivers updated. This resolves 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.
  
  
• 736703: Upgrade from ESXi 4.0.x to ESXi 4.1 using VMware Update Manager fails on IBM x3650 M2 servers.
  
  
• 747603: Virtual machine might not power on after failover in an HA cluster.
  
  
• 750983: The third-party mptsas, mpt2sas, and mptspi drivers are updated.
  
  
  Based on VMware KB 2002339