VMware
 

Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

ESX Server 3.0.2, Patch ESX-1003513: Fixes for VMotion and Clone Operations Failure, VirtualCenter Server Agent Crash, Hot Addition and Deletion of LUNs Failure, Virtual Machine Level Permissions; VirtualCenter 2.0.x Failure to Read VI 3.5 License Files

Details

Release Date: 03/06/08
Document Last Updated: 03/06/08
ac47c22a8ef4101e894b0bb3858e259a


Product Versions
ESX Server 3.0.2
Patch Classification
General
Supersedes
Virtual Machine Migration or Reboot Required
No
ESX Server Host Reboot Required
No
PRs Fixed
199062, 228202, 199832, 149699, 225523
Affected Hardware
N/A
Affected Software
Unknown
RPMs Included
hostd
Related CVE numbers
N/A

Summary

This patch fixes the following issues:

  • VMware VMotion and clone operations might fail if the source virtual machine or template has a floppy or CD-ROM image attached.

  • VirtualCenter Server Agent crashes during a LUN recovery.

  • When LUN rescans are in progress on ESX Server, hot addition and deletion of LUNs on virtual machines as Raw Device Mappings (RDMs) can fail with error messages. To complete the fix, install ESX-1003513 and ESX-1003515 .

  • The virtual machine level permissions get deleted when the hostd restarts. This happens due to a failure in validating permissions against virtual machine data that is not loaded when validation is in progress. The fix ensures that permission validations are performed after the virtual machine inventory is loaded.
  • VirtualCenter 2.0.x is not able to read the Virtual Infrastructure 3.5 license files generated from the license portal.

    • Solution

    Note: Before you begin please refer to KB1003490 for important information on restarting the mgmt-vmware service.

    Symptoms

    The following symptoms occur without this patch:

  • VMware VMotion and clone operations might fail if the source virtual machine or template has a floppy or CD-ROM image attached.

  • During a LUN recovery, VirtualCenter Server Agent crashes with an error message similar to the following:
      { [#7] dynamicType = <unset>,
        [#7] msg = "An error occurred while communicating with the remote host."
        [#7]
      }
        The HostCommunication error message is logged in /var/log/vmware/hostd.log.

  • When LUN rescans are in progress, hot addition and deletion of LUNs on virtual machines as Raw Device Mappings (RDMs) might fail with concurrent modification and file not found exceptions.

  • Virtual machine level permissions might get deleted on restart of the ESX Server host or a restart of the mgmt-vmware service on the ESX Server host. 
    The following error message might be displayed in     /var/log/vmware/hostd.log.
     
    [2007-10-03 05:35:45.715 'Vimsvc' 3076448384 info] Loading authorization data from /etc/vmware/hostd/authorization.xml
    [2007-10-03 05:35:45.758 'Vimsvc' 3076448384 error] Removing invalid permission 553: unknown entity
    [2007-10-03 05:35:45.798 'Vimsvc' 3076448384 error] Removing invalid permission 554: unknown entity  

  • VirtualCenter 2.0.x logs well formed chunk error messages in hostd and vpxd log files.

    • Deployment Considerations

    To address the issue of hot addition and deletion of LUNs on virtual machines as Raw Device Mappings (RDMs), you must install ESX-1003513  and  ESX-1003515 to complete the fix. Run service mgmt-vmware restart on ESX Server.

    Download Instructions

    Download and verify the patch bundle as follows:

    1.      Download patch ESX-1003513 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-1003513.tgz

    The md5 checksum output should match the following:

    ac47c22a8ef4101e894b0bb3858e259a ESX-1003513.tgz
     

    7.      Extract the compressed tar archive:

    # tar -xvzf ESX-1003513.tgz

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

    # cd ESX-1003513

    Installation Instructions

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

    For example, if the host is called depot:

    # esxupdate -r file:///depot/var/updates/ESX-1003513 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-1003513 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;urlz

    Feedback

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