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-200805513-BG: Update to VMware-esx-iscsi (1004649)

Details

Release Date: 03 JUNE 2008
Document Last Updated: 03 JUNE 2008

 

Download Size: 
328 KB
Download Filename:
ESX350-200805513-BG.zip
md5sum:
19032eaa11e17da0fd9b4d5b95b9a89d


Product Versions ESX Server 3.5
Patch Classification Critical
Supersedes None
Requires ESX350-200805502-BG
ESX350-200805503-BG
Virtual Machine Migration or Reboot Required Yes
ESX Server Host Reboot Required Yes
PRs Fixed 121161
Affected Hardware N/A
Affected Software N/A
RPMs Included

VMware-esx-iscsi

Related CVE numbers None


 

Solution

Summary

This patch fixes a memory access issue where the iSCSI daemon might crash when attempting to remove stale target IDs. (PR 121161)

Symptom

The iSCSI daemon dies suddenly, resulting in new targets not getting discovered on a rescan.

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 http://www.vmware.com/download/vi/vi3_patches_35.html and install the bundle using esxupdate from the command line of the host. For more information, see the ESX Server 3 Patch Management Guide.

Keywords

esx35p04

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

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