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 Server 3.5, Patch ESX350-200804404-BG: Update to VMware-esx-drivers-scsi-vmkiscsi (1004164)


Release Date: 30 APR 2008
Document Last Updated: 30 APR 2008


Download Size:
193 KB
Download Filename:

Product Versions ESX Server 3.5
Patch Classification General
Supersedes None
Requires ESX350-200804407-BG
Virtual Machine Migration or Reboot Required Yes
ESX Server Host Reboot Required Yes
PRs Fixed 202475
Affected Hardware N/A
Affected Software N/A
RPMs Included VMware-esx-drivers-scsi-vmkiscsi
Related CVE numbers None



This patch includes a fix to allow Windows virtual machines to boot when DataDigest is enabled in software iSCSI. (PR 202475)


When DataDigest is enabled for the software iSCSI initiator, certain Windows virtual machines might not boot. This situation occurs because of badly-formed I/O requests sent by the Windows guest operating system. This fix detects such I/O requests and handles them to allow the virtual machine to boot.

Deployment Considerations

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

Patch Download and Installation

See the VMware Update Manager Administration Guide for instructions on using Update Manager to download and install patches to automatically update ESX Server 3.5 hosts.

To update ESX Server 3.5 hosts when not using Update Manager, download the most recent patch bundle from and install the bundle using esxupdate from the command line of the host. For more information, see the ESX Server 3 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)
  • 0 Ratings