VMware ESXi 5.0 Patch ESXi500-201109401-BG: Updates esx-base (1027808)
Release date: September 13, 2011
|Patch Category||Bug Fix|
|Build||For build information see KB 2001075|
|Host Reboot Required||Yes|
|Virtual Machine Migration or Shutdown Required||Yes|
|VIBs Included||esx-base 5.0.0-0.3.474610|
|PRs Fixed||726523, 731820, 736366, 754081, and 756551|
|Related CVE numbers||N/A|
Summaries and Symptoms
This patch updates the esx-base VIB to resolve the following issues:
- When you are using ESXi with EMC VMAX, if storage-based hardware acceleration is enabled for vStorage APIs for Array Integration (VAAI), Storage vMotion and cloning operations might take longer to complete than when using software (host) data copy causing performance degradation.
- When two or more CIM VIBs that support WS-Management (WSMAN) are installed on an ESXi system, the openwsman init script deletes the contents of the openwsman.conf file, and the Openwsman service stops running.
- On an ESXi system, lspci or vmkvsitools lspci commands might fail with a core dump.
- When you create a snapshot of a virtual machine followed by a hot-plug operation and you revert the virtual machine to the states of the snapshot before the hot-plug operation, the virtual machine's .vmx configuration file might become corrupted. For more information about the issue, see KB 2005740.
- If vShield Endpoint driver is installed in a virtual machine and you create a snapshot of the virtual machine, a file open operation that follows the snapshot operation might take a long time to complete (upto 2 minutes). Files are not scanned when this issue occurs, making the virtual machine vulnerable.
None beyond the required patch bundles and reboot information listed in the table above.
Patch Download and Installation
The typical way to apply patches to ESXi hosts is through the VMware Update Manager. For details, see the Installing and Administering VMware vSphere Update Manager.
ESXi hosts can be updated by manually downloading the patch ZIP file from the VMware download page and installing the VIB by using the esxcli software vib command. Additionally, the system can be updated using the image profile and the esxcli software profile command. For details, see the vSphere Command-Line Interface Concepts and Examples and the vSphere Upgrade Guide.