VMware ESX Server 3.5, Patch ESX350-200804401-BG: Update to VMware-esx-vmkernel

Details

Release Date: 30 APR 2008 
Document Last Updated: 30 APR 2008

 

Download Size: 
19 MB 
Download Filename: 
ESX350-200804401-BG.zip 
md5sum: 
c2fd49d56a5afdbc449454ade5fe0365


Product VersionsESX Server 3.5
Patch ClassificationCritical
SupersedesESX350-200712409-BG
ESX350-200802412-BG
RequiresESX350-200803202-UG
ESX350-200804408-BG
Virtual Machine Migration or Reboot RequiredYes
ESX Server Host Reboot RequiredYes
PRs Fixed225552, 220682, 220844
Affected Hardware- HDS modular storage array models AMS, SMS, WMS, and 9500V
Affected SoftwareN/A
RPMs IncludedVMware-esx-vmkernel
Related CVE numbersNone


Solution

Summaries and Symptoms

Issues fixed in this patch (and their relevant symptoms, if applicable) include:

  • Spurious SysAlert warning messages appear on some systems which have less than 8 MTRRs implemented. (PR 225552)

    Symptoms: Warning messages appear that include the following text: 

    ALERT: MTRR: 461: Unsupported number of MTRRS 7


  • DHCP resets the IP address and netmask when trying to acquire or renew a lease, even though the IP address has not changed. (PR 220682)

    Symptoms: When DHCP tries to acquire or renew a lease, vmknic might lose network connectivity.

  • The previous default multipath policy for all HDS modular storage arrays such as AMS, SMS, WMS, 9500V was MRU. Because all of these arrays are either Active/Active or Pseudo Active/Active, the default path policy for these arrays has been changed to FIXED with this patch. (PR 220844)

Deployment Considerations

None beyond the required patch bundles and reboot information listed in the table, above.

Based on VMware KB 1004161

  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

Hardware and firmware requirements for 64-bit guest operating systems

PurposeThis article explains the host machine hardware and firmware requirements for installing...

Logging in to the vCenter Server 5.0 Web Client fails with the error: unable to connect to vCenter Inventory Service

DetailsAfter upgrading from vCenter Server 4.1 to 5.0, you experience these symptoms:Cannot log...

Multiple network entries in vCenter Server 5.0.x after migrating virtual machines from a virtual switch to a virtual distributed switch

SymptomsAfter migrating virtual machines from a virtual switch to a virtual Distributed...

Minimum requirements for the VMware vCenter Server 5.x Appliance

PurposeIf you are using the VMware vCenter Server Appliance, beginning with vSphere 5.0 you can...