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

ESX Server 3.0.1, Patch ESX-1002100; Updates to VMware Tools; Fixes For Detecting LSI Logic Controller, Installing vmxnet Correctly, Compilation Failure With GuestSDK Header Files (1002100)

  • 0 Ratings


Release Date: 12/03/07
Document Last Updated: 12/03/07
Download Now
Download Size: 
53.0 MB
Download Filename:

Product Versions
ESX Server 3.0.1
Patch Classification
Virtual Machine Migration or Reboot Required
ESX Server Host Reboot Required
PRs Fixed
Affected Hardware
LSI Logic SCSI cards
Affected Software
RPMs Included
VMware-esx-tools, VMware-esx-vmx
Related CVE numbers


This patch fixes the following issues:
  • Fixes an issue where pcnet32/vlance drivers are loaded instead of vmxnet drivers after VMware Tools is installed.
  • Fixes an issue where guest operating systems with Linux kernel version 2.6.18 or greater and using LSI Logic driver version 3.04.01 or greater do not detect the LSI Logic controller.
  • Fixes an issue where compilation failed when including GuestSDK header files, as the file includeCheck.h referenced by GuestSDK headers was missing from 64-bit Windows Tools installation. This fix adds includeCheck.h to the GuestSDK install.



The following symptoms might be seen in systems without this patch:
  • vmxnet driver is the default network driver that is installed with VMware Tools. However, after installing VMware Tools and restarting the virtual machine, checking the network driver by using lsmod might display pcnet32 or vlance driver as the default driver. Further, using lsmod might display vmxnet as unused:

    [root@ root] # lsmod
    Module Size Used by Tainted: PF

    vmxnet 9836 0 (unused)
    vmmemctl 8204 0 (unused)
    udf 97408 0 (autoclean)

  • Installation of guest operating systems with Linux kernel version 2.6.18 or greater using LSI Logic driver version 3.04.01 or greater might fail with the following message:

    An error has occurred - no valid devices were found on which to create a file systems. Please check your hardware for the cause of this problem
  • Compilation failure when including GuestSDK header files might occur in the following scenario:

    1. Create a 64-bit Windows virtual machine (win2k3e).
    2. Install VMware Tools on the virtual machine.
    3. Install any 64-bit application, for example Visual Studio, on the virtual machine.
    4. Create a new project and add vmGuestLibTest.c to the source files. Add all three header files.
    5. Build the project. The compilation fails and an error message similar to the following might be displayed:

    Error: not able to find file #includeCheck.h

Deployment Considerations

Applying the patch will affect all LSI Logic SCSI cards.

Download Instructions

Download and verify the patch bundle as follows:

1. Download patch ESX-1002100 from .

2. Log in to the ESX Server service console as root.

3. Create a local depot directory.

# mkdir -p /var/updates

Note: VMware recommends that you use the updates directory.

4. Change your working directory to /var/updates .

# cd /var/updates

5. Download the tar file into the /var/updates directory.

6. Verify the integrity of the downloaded tar file:

# md5sum ESX-1002100.tgz

The md5 checksum output should match the following:

534682427005470c35968be49bff169a ESX-1002100.tgz

7. Extract the compressed tar archive:

# tar -xvzf ESX-1002100.tgz

8. Change to the newly created directory, /var/updates/ESX-1002100 :

# cd ESX-1002100

Installation Instructions

Note: All virtual machines on the host must be either shut down or migrated using VMotion before applying the 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-1002100 update

For example, if the host is called depot:

# esxupdate -r file:///depot/var/updates/ESX-1002100 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-1002100 update

For more information how to use esxupdate, see the Patch Management for ESX Server 3 tech note 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.


  • 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)

Please enter the Captcha code before clicking Submit.
  • 0 Ratings