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

VMware ESX Server 3.5, Patch ESX350-200802412-BG: Updates to the VMkernel to Fix Networking and Hardware Issues (1003459)

  • 1 Ratings


Release Date: 3/10/2008
Document Last Updated: 4/16/2008 - updated Deployment Considerations section


Download Size:
19.4 MB
Download Filename:

Product Versions ESX Server 3.5
Patch Classification General
Supersedes ESX350-200712409-BG
Virtual Machine Migration or Reboot Required Yes
ESX Server Host Reboot Required Yes
PRs Fixed 221857, 201812, 199127, 220712, 200222, 224030, 220646, 236942, 199832, 182778
Affected Hardware
- Intel Zoar NICs
- Systems with Intel Penryn family processors
- Systems with mixed stepping CPUs, which includes those with dual-core Intel Xeon 5100-series (Woodcrest) and quad-core Intel Xeon 5300-series (Clovertown) processors
- Systems with dual-core Intel Xeon 7200-series processors
Affected Software Dell OpenManage Array Manager (OMSS)
RPMs Included
Related CVE numbers None


This patch provides fixes for the following issues:
  1. Because of on-disk corruption during the consolidation of snapshots, virtual machines (typically Windows) under heavy disk workload stop responding and display a blue screen.

  2. /proc/vmware/cpuinfo and /proc/cpuinfo report incorrect information for Intel Penryn family processors.

  3. Due to a possible race in the device file system code, ESX Server might stop responding when loading and unloading storage drivers.

  4. An issue in the skb_copy implementation in vmklinux, which is a module that allows Linux device drivers to run in the VMkernel.

  5. The REPORT LUNS SCSI command sometimes returns an incorrect value.

  6. Fixes ESX Server support for Intel Zoar NICs on a VLAN trunking configuration. A flaw exists between the ESX Server networking subsystem and the igb driver.

  7. On systems with mixed stepping CPUs, ESX Server prints out spurious warning messages in /var/log/vmkwarning.

  8. A fix to allow Dell OMSS to report events from the RAID controller accurately.

  9. Simultaneous rescans and the hot addition or deletion of RDMs can sometimes fail.

  10. VirtualCenter does not properly record the number of processors on hosts with dual-core Intel Xeon 7200-series processors.



  1. While running performance and benchmarking applications like IOzone or MemHog, and while performing snapshot consolidate operations, virtual machines stop responding, with a blue screen that reports KERNEL_STACK_INPAGE_ERROR or SYSTEM_SERVICE_EXCEPTION (77).

  2. Incorrect CPU information is reported for Intel Penryn family processors.

  3. ESX Server stops responding when it loads and unloads storage device drivers. Incorrect output might appear when you run vdf –h /vmfs/devices to determine the current space.

  4. The skb_copy() function of the vmklinux module does not work as expected. In rare cases, the transmit packets are corrupted.

  5. A malformed REPORT LUNS command (for example, possibly created by a faulty application or SCSI utility in the guest) might sometimes return incorrect status.

  6. When implementing a VLAN trunking configuration on an ESX Server system that utilizes the igb driver for Intel Zoar NICs, connectivity is lost.

  7. On systems with mixed stepping CPUs, /var/log/vmkwarning displays messages that look like the following:

    vmkernel: 0:00:00:00.XXX cpuX:XXX)WARNING: Cpu: SaveAndCheckCPUID:518: version 000006fb but BSP 000006f7

    These messages are harmless and can be ignored. This patch version moves the messages from warnings in /var/log/vmkwarning to informational messages in /var/log/vmkernel.

  8. The status of failed and rebuilding drives is not displayed correctly in Dell OMSS.

  9. While performing simultaneous rescans and the hot addition or deletion of RDMs (or other such operations that involve RDM creation, RDM open, or RDM deletion), the procedure might sometimes fail. The system reports the exceptions "concurrent modification" and "file not found" in /var/vmware/log/hostd.log. After applying the patch, the system might still report the "concurrent modification" exception. If this occurs, retry the operation. You should not see the "file not found" exception after applying the patch.

  10. When connecting to an ESX Server host running with one or more dual-core Intel Xeon 7200-series processors installed, VirtualCenter under-reports the number of processor sockets available. Due to the under-reported number of sockets, some sockets that are operating on the ESX Server host are unlicensed.

Deployment Considerations

Patch bundles ESX350-200802403-BG and ESX350-200802409-BG must be installed prior to installing this patch. The esxupdate utility will check to ensure that ESX350-200802403-BG and ESX350-200802409-BG are installed before proceeding with installation of this patch.
For dual-core Intel Xeon 7200-series processors:
  • ESX Server is licensed on a per-CPU-package basis. ESX Server previously recognized certain dual-core CPUs as half of a quad-core CPU package. ESX Server hosts with these CPUs recognized one license for each two CPU packages. This fix enables such ESX Server hosts to require one license for each CPU package.
  • Make sure your license server has sufficient ESX Server licenses available before installing this patch.

Patch Download and Installation

To automatically download and install patches on your ESX Server 3.5 hosts, use the VMware Update Manager. For more information, see the Update Manager Administration Guide at

To update ESX Server 3.5 hosts from the command line of the service console, download the most recent patch bundle from and install it using the esxupdate utility. For more information about using esxupdate, see the ESX Server 3 Patch Management Guide at

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.


  • 1 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.
  • 1 Ratings