Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

Search the VMware Knowledge Base (KB)

View by Article ID

ESX Server 3.0.2, Patch ESX-1008405: ESX Server Might Stop Responding as Cache Is Cleared for Pages from Virtual e1000 Driver; Fix for NOT_IMPLEMENTED error triggered by guest LSI drivers

Details

Release Date: 03/31/09

Document Last Updated: 06/17/09

Download Size:
40 MB
Download Filename:
ESX-1008405.tgz
md5sum:

87e4a7027b44a7d27ee2b3a7e9506afb

Product Versions	ESX Server 3.0.2
Patch Classification	General
Supersedes	ESX-1007670
Virtual Machine Migration or Reboot Required	Yes
ESX Server Host Reboot Required	Yes
PRs Fixed	351635, 350521
Affected Hardware	None
Affected Software	Virtual e1000 NIC driver
RPMs Included	VMware-esx-apps, VMware-esx-vmkernel, VMware-esx-vmx
Related CVE numbers	N/A

Summary

This patch fixes the following issues:

Virtual e1000 NIC driver might cause ESX Server to stop responding mentioning routine E1000MapGuestPACommon in the stack trace. The fix verifies whether cache for pages to be mapped is cleared and releases acquired resources.

In previous releases of ESX Server, if a guest operating system device driver queried the LSI Logic Host Bus Adapter for an unrecognized configuration page, the virtual machine terminated with a ProcessConfigPageRequest: Invalid PageType error in the vmware.log file (/vmfs/volumes/<datastore ID>/<name of virtual machine>. Refer to the detailed error message in Symptoms section.

This behavior was seen rarely with Linux and Windows guest operating systems, occasionally with Solaris guest operating systems, and regularly with the unsupported SCO OpenServer Release 5 guest operating system. Starting with this release, the issue is fixed.

Solution

Symptoms

A sample error message is as follows:

Nov 19 17:31:56.991: vcpu-0| LSI: ProcessConfigPageRequest: Invalid PageType [8] pageNo 4 Action 0
Nov 19 17:31:56.992: vcpu-0| NOT_IMPLEMENTED /build/mts/release/bora-32039/bora/devices/lsilogic/lsilogic.c:2572

Deployment Considerations

None

Download Instructions

Download and verify the patch bundle as follows:

Download patch ESX-1008405 from http://www.vmware.com/download/vi/vi3_patches.html .
Log in to the ESX Server service console as root.
Create a local depot directory.

# mkdir -p /var/updatesNote: VMware recommends that you use the updates directory.
Change your working directory to /var/updates.

# cd /var/updates
Download the tar file into the /var/updates directory.
Verify the integrity of the downloaded tar file:

# md5sum ESX-1008405.tgz

The md5 checksum output should match the following:

87e4a7027b44a7d27ee2b3a7e9506afb ESX-1008405.tgz
Extract the compressed tar archive:

# tar -xvzf ESX-1008405.tgz
Change to the newly created directory, /var/updates/ESX-1008405:

# cd ESX-1008405

Installation Instructions

Note: All virtual machines on the host must be either shut down or migrated using VMotion before applying the patch. A reboot of the ESX Server host is required after applying this patch.

After you download and extract the archive, and if you are in the directory that you previously created, use the following command to install the update:

# esxupdate update

To run esxupdate from a different directory, you must specify the bundle path in the command:

# esxupdate -r file://<directory>/ESX-1008405 update

For example, if the host is called depot:

# esxupdate -r file:///depot/var/updates/ESX-1008405 update

During the update process, logs appear on the terminal. You can specify the verbosity of esxupdate logs by using the -v option as shown, below.

# esxupdate -v 10 file://<directory>/ESX-1008405 update

For more information on how to use esxupdate, see the Patch Management for ESX Server 3 tech note at http://www.vmware.com/pdf/esx3_esxupdate.pdf.

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

1 2 3 4 5

1 2 3 4 5

Actions

Bookmark Document

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)