VMware ESXi 5.0,Patch Release ESXi500
本帖最后由 TiGi 于 12-16-2011 20:18 编辑Release Date: December 15, 2011
Download Filename:
ESXi500-201112001.zip
Build:
515841
Download Size:
297.7 MB
md5sum:
107ec1cf6ee1d5d5cb8ea5c05b05cc10
sha1sum:
aff63c8a170508c8c0f21a60d1ea75ef1922096d
Host Reboot Required: Yes
Virtual Machine Migration or Shutdown Required: Yes
Bulletin ID Category Knowledge Base Article
ESXi500-201112401-SG Security 2007671
ESXi500-201112402-BG Bug Fix 2007672
ESXi500-201112403-SG Security 2007673
ESXi500-201112404-BG Bug Fix 2007674
ESXi500-201112405-BG Bug Fix 2007675
Image Profile Filenames:
ESXi-5.0.0-20111204001-standard
ESXi-5.0.0-20111204001-no-tools
Image Profile Name Knowledge Base Article
ESXi-5.0.0-20111204001-standard 2009330
ESXi-5.0.0-20111204001-no-tools 2009334
Solution
Summaries and Symptoms
This patch release contains the bug fixes for ESXi. For more information, see the KB articles for the individual bulletins.
For information about the issues fixed with the ESXi-5.0.0-20111204001-standard image profile, see KB 2009330.
For information about the issues fixed with the ESXi-5.0.0-20111204001-no-tools image profile, see KB 2009334.
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.
http://www.vmware.com/patchmgr/findPatch.portal
本帖最后由 TiGi 于 12-16-2011 20:23 编辑
VMware ESXi 5.0 Patch ESXi500-201112405-BG: Updates net-be2net
Summaries and Symptoms
This patch updates the net-be2net VIB to resolve an issue where, when using vSphere 5.0 with Emulex BE2/BE3 NICs (be2net driver) in a HP FlexFabric/Flex-10 or IBM Virtual Fabric Adapter (VFA) environment, connectivity may not work properly on Windows VMs or the server when VLANs are configured.
Deployment Considerations
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.
VMware ESXi 5.0 Patch ESXi500-201112403-SG: Updates net-e1000 and net-e1000e
Summaries and Symptoms
This patch updates the net-e1000 and net-e1000e VIB to resolve a security issue in the e1000 and e1000e Linux drivers for Intel PRO/1000 adapters that allows a remote attacker to bypass packet filters and send manipulated packets.
The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2009-4536 to this issue. 本帖最后由 TiGi 于 12-16-2011 20:24 编辑
VMware ESXi 5.0 Patch ESXi500-201112404-BG: Updates misc-drivers
Summaries and Symptoms
This patch updates the misc-drivers VIB to resolve an issue where if software FCoE drivers are used with NICs that support partial FCoE offload, the ESXi host might fail to boot on Cisco's UCS rack-mount servers and stops responding with a backtrace similar to the following on the purple screen:
#0 0x0000000000000000 in ?? ()
#1 0x000041801763f8f9 in fcoe_ctlr_l2_link_ok (work=0x410013404eb0) at vmkdrivers/src_9/drivers/scsi/fcoe/libfcoe.c:1419
#2 fcoe_ctlr_timer_work (work=0x410013404eb0) at vmkdrivers/src_9/drivers/scsi/fcoe/libfcoe.c:1460
#3 0x000041801744e98d in vmklnx_workqueue_callout (data=)
at vmkdrivers/src_9/vmklinux_9/vmware/linux_workqueue.c:690
#4 0x0000418016c611d8 in helpFunc (data=) at bora/vmkernel/main/helper.c:3213
#5 0x0000000000000000 in ?? ()
VMware ESXi 5.0 Patch ESXi500-201112402-BG: Updates tools-light
Summaries and Symptoms
This patch updates the tools-light VIB to update the pre-built kernel driver modules for Ubuntu 10.04.3, Ubuntu 11.04, and Ubuntu 11.10. In addition, it also resolves the following issues:
When VMware Tools installed on a Windows XP virtual machine running on an ESXi 5.0 host patched with ESXi500-201109001 is upgraded using the automatic upgrade option, a warning message similar to the following might be displayed in the Software Installation window of the virtual machine:
The software you are installing has not passed Windows Logo testing to verify its compatibility with Windows XP.
This issue also occurs when VMware Tools is installed by using the Install/Upgrade Tools option and selecting the complete mode, or custom mode with LSI driver selected.
When vShield Endpoint driver is installed using the VMware Tools installer, the Endpoint driver might fail to load (before the virtual machine is rebooted) as it is installed before the VMCI driver is installed and loaded. This patch resolves the issue by installing the VMCI driver before installing the Endpoint driver.
When a virtual machine with Windows 2003 guest operating system is installed with a Windows XP display driver model (XPDM) driver, the virtual machine might stop responding with a malloc() in vmx_fb.dll error and fails with a blue screen and STOP 8E vmx_fb.dll error.
This patch updates the VMware display driver version to 11.7.10.0.
VMXNET 3 driver versions 1.0.25.0-k to 1.1.17.0-k fail to activate the device if the number of vCPUs that you assign to a virtual machine is not a power of two. You might see an error message similar to the following while running the demsg command:
Failed to activate dev eth0:error 1
An error message similar to the following might be written to vmware.log:
VMXNET3 user: failed to activate Ethernet1 with status 0xbad0007 VMware ESXi 5.0 Patch ESXi500-201112401-SG: Updates esx-base
Summaries and Symptoms
This patch updates the esx-base VIB to resolve the following issues:
Updates the glibc third party library to resolve multiple security issues.
The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2010-0296, CVE-2011-0536, CVE-2011-1071, CVE-2011-1095, CVE-2011-1658 and CVE-2011-1659 to these issues.
When a hot spare disk that is added to a RAID group is accessed before the disk instance finishes initialization or if the disk is removed while an instance of it is being accessed, a race condition might occur causing the vSphere Client to not display information about the RAID controllers and the vSphere Client user interface might also not respond for a very long time.
vMotion fails with the A general system error occurred: Failed to flush checkpoint data! error message when:
The resolution of the virtual machines is higher than 1280x1024, or smaller if you are using a second screen
The guest operating system is using the WDDM driver (Windows 7, Windows 2008 R2, Windows 2008, Windows Vista)
The virtual machine is using Virtual Machine Hardware version 8.
Creating host profiles of ESX i 5.0 hosts might fail when the host profile creation process is unable to resolve the hostname and IP address of the host by relying on the DNS for hostname and IP address lookup. An error message similar to the following is displayed:
Call"HostProfileManager.CreateProfile" for object "HostProfileManager" on vCenter Server" failed.
Error extracting indication configuation: Name or service not known.
In vSphere 5.0, Thin Provisioning is enabled by default on devices that adhere to T10 standards. On such thin provisioned LUNs, vSphere issues SCSI UNMAP commands to help the storage arrays reclaim unused space. Sending UNMAP commands might cause performance issues with operations such as snapshot consolidation or storage vMotion.
This patch resolves the issue by disabling the space reclamation feature, by default.
If a user subscribes for an ESXi Server’s CIM indications from more that one client (for example, c1 and c2) and deletes the subscription from the first client (c1), the other clients (C2) might fail to receive any indication notification from the host.
This patch also provides you with the option of configuring the iSCSI initiator login timeout value for software iSCSI and dependent iSCSI adapters.
For example, to set the login timeout value to 10 seconds you can use commands similar to the following:
~ # vmkiscsi-tool -W -a "login_timeout=10" vmhba37
~ # esxcli iscsi adapter param set -A vmhba37 -k LoginTimeout -v 10
The default login timeout value is 5 seconds and the maximum value that you can set is 60 seconds.
We recommend that you change the login timeout value only if suggested by the storage vendor. thank for info 谢谢提供。补丁还真多 今天正好是周末，如果遇到上述提到的问题，或者可以考虑升级/更新。 视乎没人下载 现在还是自己在玩,没上Prod,补丁无所谓哇.
页:
[1]