VMware
 

Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

ESX Server 3.0.2, Patch ESX-1005105: Fix for Data Loss in Serial Ports; IBM SVC Returns Check Condition Error; Warning Messages Appear After Installing HP Insight Management Agents 7.90; Fix for an issue in IDE Emulation; Applications in VMs return Error

Details

Release Date: 07/08/08
Document Last Updated: 07/08/08
 
c9dc13e2ead2f2165f94b8dd972a312d
Product Versions
ESX Server 3.0.2
Patch Classification
Critical
Supersedes
Virtual Machine Migration or Reboot Required
Yes
ESX Server Host Reboot Required
Yes
PRs Fixed
194416, 258065, 199274, 217696, 251076
Affected Hardware
N/A
Affected Software
Unknown
RPMs Included
VMware-esx-vmx, VMware-esx-vmkernel, VMware-esx-apps
Related CVE numbers
N/A

Summary

This patch fixes the following issues:  
  • Sending fax from a virtual machine using the serial port on the ESX Server host causes data loss such as missing lines and unclear information. This fix is activated by adding serial<n>.hardwareFlowControl = “TRUE” to the vmx file after patch installation.
     
  • IBM SAN Volume Controller (SVC) returns the Check Condition 0/2 5 25 0 error code when a LUN is unmapped. This fix allows ESX Server to mark the paths to unmapped LUNs as inactive.
     
  • Warning messages appear in the vmkwarning log file after installing HP Insight Management Agent version 7.90 on ESX Server.
     
  • 32-bit application running in compatibility mode, which uses Binary Translation (BT), on a 64-bit virtual machine displays an error message. This fix ensures that 32-bit applications running in compatibility mode uses Virtualisation Technology (VT). 

Solution

Symptoms

The following issues might occur without this patch:
  • Data loss such as missing lines and unclear information is observed in faxes received from virtual machines using the serial port.
     
  • The IBM LUN will not be marked when the LUN is unmapped (i.e. no failover occurs).   
     
  • Warning messages similiar to the following are generated in the vi/var/log/vmkwarning log file:
    Sep 4 10:21:22 hostname vmkernel: 0:00:04:24.610 cpu1:1038)WARNING: Util: 694: No memory?
    Sep 4 10:21:27 hostname vmkernel: 0:00:04:29.616 cpu1:1038)WARNING: Util: 694: No memory?
    Sep 4 10:21:27 hostname vmkernel: 0:00:04:29.626 cpu1:1038)WARNING: Util: 694: No memory?
     
  • Sunbelt Ninja installed on a 64-bit virtual machine stops responding due to random access violations and displays an error message similiar to the following:
    Win 2003 64bit /vmfs/volumes/45c780d5-21892cb8-b83b-0017a4770024/WINMAIL1/WINMAIL1.vmx
     

Deployment Considerations

N/A 

Download Instructions

Download and verify the patch bundle as follows :

1.      Download patch ESX-1005105 from http://www.vmware.com/download/vi/vi3_patches.html .
 
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-1005105.tgz

The md5 checksum output should match the following:

c9dc13e2ead2f2165f94b8dd972a312d ESX-1005105.tgz
 

7.      Extract the compressed tar archive:

# tar -xvzf ESX-1005105.tgz

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

# cd ESX-1005105

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-1005105 update

For example, if the host is called depot:

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

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

Keywords

esxpatch;esx302

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (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? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   
Actions
  • KB Article: 1005105
  • Updated: Aug 14, 2009
  • Products:
    VMware ESX
  • Product Versions:
    VMware ESX 3.0.x