Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

ESX350-200803202-UG Patch; Multiple RPM Updates, Including VMware-esx-tools, VMware-esx-vmkernel, and VMware-hostd-esx (1003696)

Details

Release Date: 4/10/2008
Document Last Updated: 4/10/2008
Download Size: 206 MB
Download Filename:
ESX350-200803202-UG.zip
md5sum:
62189e9967144cdaecdffba3035dfe66


Product Versions ESX Server 3.5 Update 1
Patch Classification General
Supersedes

ESX350-200712409-BG, ESX350-200802411-BG, ESX350-200802412-BG, ESX350-200712410-BG, ESX350-200802401-BG

Virtual Machine Migration or Reboot Required Yes
ESX Server Host Reboot Required Yes
PRs Fixed 145188, 204434, 216142, 221502, 222681, 224122, 230338, 231006, 233212, 233351, 234296, 235315, 236078, 236475, 236942, 243246
Affected Hardware All supported hardware platforms
Affected Software ESX Server 3.5 Classic and ESX i3.5
RPMs Updated VMware-esx-tools, VMware-esx-vmkernel, VMware-hostd-esx, VMware-esx-apps, VMware-esx-tools, VMware-esx-vmkctl, VMware-esx-vmx
Related CVE numbers N/A

Summary

This patch provides fixes for the following issues:
  1. Virtual machines that are powered off cannot be unregistered from an ESX Server host that is in maintenance mode.
  2. Support for virtual machine names with non-ASCII characters.
  3. When deleting snapshots, virtual machines with heavy I/O load might cause the hostd service to stop responding. This issue might also result in the VI Client getting disconnected from the ESX Server host.
  4. VMware VMotion completed successfully but memory resources on the source ESX Server host are not released.
  5. Failed SCSI release command can crash ESX Server host. The fix is for correctly handling the failure on release command.
  6. When performing a VMware VMotion to a VMvisor host in an over-committed-memory situation, the destination host stops responding and the failed migration does not recover on the source host.
  7. Fixes a network connectivity issue where packets with an 802.2LLC header (without SubNetwork Access Protocol (SNAP)) are dropped by the vmxnet driver in ESX Server 3.5. This issue has been observed with NetBEUI and SNA/DLC protocols.
  8. Virtual machine Power User cannot connect to a remote CD-ROM or floppy device.
  9. ESX Server host stops responding due to insufficient COW heap size. This fix allows users to configure the maximum COW heap size.
  10. Some OEM installation CDs won't work. The fix is for Microsoft Windows Virtual System Locked Pre-installation (SLP) certificate from the second to the first OEM SMBIOS string.
  11. Message Signaled Interrupts (MSI/MSI-X) are not fully supported on ESX Server 3.5. This fix disables MSI/MSI-X by default unless NetQueue is enabled.
  12. The Cisco Discovery Protocol (CDP) parsing code in the VMkernel does not support VLAN tags on CDP packets. As a result, all CDP packets received with VLAN tags are ignored and ESX Sever 3.5 does not detect CDP information. The CDP parsing code in the VMkernel did not support VLAN tags on CDP packets. The issue has been observed on some Cisco switches when the Native VLAN is changed to something other than 1.
  13. In rare cases, virtual machines running certain guest operating systems, for example SUSE Linux Enterprise Server SP3, might be terminated.

  14. CDP is enabled (listen mode) on the vswitch by default when it is created. This results in passing of Virtual Infrastructure Client and VirtualCenter Server garbage values in the OID field of the CDP packets, which causes the VI Client and the VirtualCenter Server to stop responding.
  15. Allows Dell OpenManage Array Manager (OMAM) to report events from the RAID controller accurately.
  16. Stopping and starting the mgmt-vmware service might cause an unexpected reboot of virtual machines that are configured to automatically stop or start.

Solution

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

Symptoms

  1. Trying to unregister virtual machines on ESX Server hosts without this fix, generates an error message:

    A general system error: Invalid fault

  2. No user-visible symptoms.
  3. While deleting snapshots, the hostd stops responding. This error might be displayed:

    Request failed because the remote server took too long to respond

  4. The VMX process does not exit on the source ESX Server host. The message vmx| VMX has left the building: 0.might be missing from the end of the source VMX's log file.
  5. ESX Server host crashes.
  6. No user-visible symptoms.
  7. When running ESX Server in debug mode, each dropped packet produces the message
    drop %p
    Net: Vmxnet2VMKDevPollTxRing:2523: drop 0x75fbcc0

     

  8. The issue with connectivity to a remote CD-ROM or floppy device might happen in this scenario:
    1. Assign virtual machine "Power User" role to a test user on a single virtual machine
    2. Log in to the VI Client as test user.
    3. Select the virtual machine, click on the Console tab, click the Connect CD/DVD button. The operation might fail with the error:

      Vmomi.Fault.NoPermission: Permission to perform this operation was denied
  9. In a situation where the COW Heap gets exhausted quickly, warning messages are generated from COW code, indicating the COW heap is low, followed by a crash of the ESX Server host. The VMkernel warning messages might look similar to:

    Mar 19 16:12:43 localhost vmkernel: 0:00:20:57.137 cpu2:1077)Heap: 1856: cow: heap below 4% -- 10968128 bytes free
    Mar 19 16:12:43 localhost vmkernel: 0:00:20:57.088 cpu2:1086)WARNING: Heap: 1445: Heap cow could not be grown to accomodate the memory request
    Mar 19 16:12:43 localhost vmkernel: 0:00:20:57.088 cpu2:1086)WARNING: Heap: 1522: Heap_Align(cow, 458752/458752 bytes, 4 align) failed. caller: 0x9da248
    Mar 19 16:12:43 localhost vmkernel: 0:00:20:57.088 cpu2:1086)WARNING: Cow: 576: No memory available! Called from 0x9da248


    When the COW heap is exhausted you won't be able to power on virtual machines. So when they cannot power on a virtual machine, you should check the var/log/vmkernel file to see if there are any messages indicating that COW heap has been exhausted. Based on this, the COW heap can be reconfigured.

  10. Some OEM install CDs won't install.
  11. No user-visible symptoms.
  12. No user-visible symptoms.
  13. In rare cases the virtual machine running certain guest operating systems, for example, SUSE Linux Enterprise Server SP3, might terminate with this error in the vmware.log file:

    vcpu-0:VMM fault: regs=0x2f8c, exc=13, eip=0x10da8b
  14. No user-visible symptoms.
  15. The status of failed and rebuilding drives is not displayed correctly in Dell OMAM.
  16. Manually stopping or starting the mgmt-vmware service (hostd) through the service console causes virtual machines that are set to automatically start or stop to unexpectedly reboot.

Deployment Considerations

You must also install ESX350-200803208-UG to complete the fix for the issues addressed by this patch.

Patch Download and Installation

For information on using VMware Update Manager to automatically update ESX Server 3.5 hosts see the VMware Update Manager Administration Guide  for instructions on using Update Manager to download and install patches.

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 the the esxupdate tool from the command line of the host. For more information on using esxupdate to manage patches on ESX Server 3.5 hosts, see the ESX Server 3 Patch Management Guide .

Keywords

esxpatch;esx35U1;urlz

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

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