VMware ESX 3.5, Patch ESX350-201012401-SG: Updates VMkernel, hostd, and VMX

Details

Release Date: December 7, 2010

Download Size
139.8MB
Download Filename
ESX350-201012401-BG.zip
md5sum:
a8b1d9e4eabd14b6822bd1f8bf6dbf69 
Product VersionsESX 3.5
Build317866
Patch ClassificationSecurity
SupersedesESX350-200712405-SG
ESX350-200712409-BG
ESX350-200712410-BG
ESX350-200802305-SG
ESX350-200802401-BG
ESX350-200802411-BG
ESX350-200802412-BG
ESX350-200803203-UG
ESX350-200804401-BG
ESX350-200804402-BG
ESX350-200804403-BG
ESX350-200806401-BG
ESX350-200806405-BG
ESX350-200806812-BG
ESX350-200808203-UG
ESX350-200901401-SG
ESX350-200904201-SG
ESX350-200904408-SG
ESX350-200905401-BG
ESX350-200905402-BG
ESX350-200906408-BG
ESX350-200907404-BG
ESX350-200907407-BG
ESX350-200908405-BG
ESX350-200908406-BG
ESX350-201008401-SG
RequiresESX350-200911201-UG
ESX350-201006401-SG
ESX350-201006409-BG
ESX350-201012404-BG
ESX350-201012410-BG
Virtual Machine Migration or Reboot RequiredYes
Host Reboot RequiredYes
PRs Fixed534645, 576968, 317194, 544645, 535896,  553413
Affected HardwareN/A
Affected SoftwareN/A
RPMs IncludedVMware-cim-esx
VMware-esx-apps
VMware-esx-backuptools
VMware-esx-uwlibs
VMware-esx-vmkernel
VMware-esx-vmx
VMware-hostd-esx
openssl
Related CVE NumbersCVE-2009-0590, CVE-2009-2409, CVE-2009-3555

Solution

Summaries and Symptoms

This patch fixes the following issues:

  • ESX hosts might fail to boot after you install the patch bundle ESX350-201002411-BG on Fujitsu Siemens PRIMERGY RX600 S2 and RX600 S3 systems with installed DVD-ROM drive. For more information about the issue,
    You can disable SATA in the BIOS so that the DVD-ROM drive is not accessible on Fujitsu Siemens PRIMERGY RX600 S2 and RX600 S3 systems. Apply this patch and enable SATA in the BIOS. After applying this patch, the following error message might appear on the service console when Fujitsu Siemens PRIMERGY RX600 S2 and RX600 S3 systems boot: cpu4:1040)Mod: 1413: Initialization for ata_piix failed with -19. You can ignore the error message and Fujitsu Siemens PRIMERGY RX600 S2 and RX600 S3 systems boot.
  • ESX hosts might fail to load VMFS volumes and then might stop responding. The VMkernel.log contains the following error messages: 

    Sep 16 08:47:21 bicvhesx06 vmkernel: 7:23:32:02.310 cpu5:1040)WARNING: J3: 1440: No space for journal on volume 4bffac9c-c5e670c8-3045-001a4bcff815. Opening in read-only mode with limited write support.
    Sep 16 08:47:21 bicvhesx06 vmkernel: 7:23:32:02.310 cpu5:1040)WARNING: J3: 1443: Set 'OpenWithoutJournal' advanced option to 0 to attempt freeing up space for journal. If this fails, volume is not opened. 


    This issue occurs due to a journal block leak in the VMFS module. This issue is fixed in the VMFS module in ESX hosts. 
  • Linux virtual machines with VMXNET2 virtual NIC adapters might fail when using MTU greater than the standard MTU of 1500 bytes (jumbo frames). 
  • When you reboot a Linux virtual machine from within the guest operating system, the virtual machine might shut down. The vmware.log file for the affected virtual machines contains the following messages:
    vcpu-0| Msg_Post: Error
    vcpu-0| [msg.log.monpanic] *** VMware ESX internal monitor error ***
    vcpu-0| vcpu-0:VMM fault: regs=0x2f94, exc=0, eip=0x84c91 

    RHEL 5 is not affected.

    The issue occurs when the monitor hits a divide-by-zero exception and fails when you reboot the guest operating system, causing the virtual machine to stop running. 
  • Certain UI applications such as the VI Client and Microsoft PowerPoint might display distorted or missing text when you view them on a VMware View hosted desktop on ESX 3.5 hosts. 
  • Deployment Considerations
None beyond the required patch bundles and reboot information listed in the table, above.

Based on VMware KB 1029993

  • 0 Els usuaris han Trobat Això Útil
Ha estat útil la resposta?

Articles Relacionats

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...