VMware ESXi 5.0, Patch ESXi500-201207401-BG: Updates esx-base (2019108)
Release date: July 12, 2012
|Patch Category||Bug Fix|
|Build||For build information, see KB 2019107.|
|Host Reboot Required||Yes|
|Virtual Machine Migration or Shutdown Required||Yes|
|PRs Fixed||830291, 831801, 835040, 836632, 838922, 838946, 842743, 843922, 847128, 848382, 853333, 855177, 855196, 862428, 863115, 866810.|
|Related CVE numbers||NA|
Summaries and Symptoms
This patch updates the esx-base VIB to resolve the following issues:
- PR 830291: An attempt to delete a file from a directory with more than 468 files or to delete the directory itself might fail, and the ESXi host might erroneously report that the VMFS is corrupted. The ESXi host logs error messages similar to the following to the /var/log/vmkernel.log file:
cpu10:18599)WARNING: Fil3: 10970: newLength 155260 but zla 2
cpu10:18599)Fil3: 7054: Corrupt file length 155260, on FD <70, 93>, not truncating
- PR 831801: The default value of FIN_WAIT_2 timer was erroneosly set to TCPTV_KEEPINTVL * TCP_KEEPCNT = 75* 0x400. This discrepancy results in the socket at FIN_WAIT_2 state to exist for a much longer time and if multiple such sockets are accumulated, they might impact new socket creation.
- PR 835040: An ESXi host might not respond or get disconnected due to the esx.conf file being locked. This might happen because when updating the ESX configuration (esx.conf configuration file) a lock file /etc/vmware/esx.conf.LOCK is created and it is linked to the process attempting to lock the file. If the link (known as a symlink) is not valid then it prevents the esx.conf from being unlocked.
- PR 836632: An ESXi host might not get added to Active Directory when DNS domain suffix differs from the Active Directory Domain Name suffix.
- PR 838922: An ESXi host might not restart UDP logging after a temporary interruption that might be caused by target server reboot or network UDP package being lost.
- PR 838946: During the installation of Windows Server 2012 or Windows 8 64-bits virtual machine, the virtual machine displays a black screen with a loading icon and stops responding during the start-up process.
Note: If using Windows Consumer Preview version, after you promote a Windows Server 2012 or Windows 8 64-bits virtual machine as a domain controller, rebooting the virtual machine causes the virtual machine to stop responding and display a black screen during the start-up process.
- PR 842743: A host profile with non-default advanced Syslog settings might fail to apply for a stateless host.
- PR 843922: If a virtual machine has a serial device that has been configured to send or receive via Virtual Serial Port Concentrator(vSPC) and if the vSPC is not running or unreachable then vmotion might fail with the following error:
The serial port concentrator did not acknowledge the migration within the allowed time limit. Module Migrate power on failed.
The default time to detect vSPC connectivity failure might be as high as two hours. This patch adds configuration variables that allow you to alter time taken for detection of vSPC connectivity failure. To set the minimum time taken to detect vSPC connectivity failure use the following steps:
- Power off the virtual machine.
- Access the ESX service console using an SSH client.
- Identify the datastore for the virtual machine that you need to set the VMX configurable options and open the virtual machine configuration file (.vmx) using vi editor. For further instructions on editing .vmx files refer to KB 1714
Locate your VSPC serial device, such as serial0 and add the configuration elements keepIdle and vmotionLimit by adding following lines below to serial0 lines in .vmx configuration file.serial0.keepIdle = 5
serial0.vmotionLimit = 25000
serial0 is an example of vSPC virtual device
keepIdle value is 5 seconds
vmotionLimit value is 25000 milliseconds
- Save the .vmx configuration file.
- Power on the virtual machine.
- PR 847128: Health Status of an ESXi host might fail to indicate when the sfcbd process stalls as the Heartbeat-Provider becomes unresponsive due to memory leaks.
- PR 848382: An ESXi host might become unresponsive with a purple diagnostic screen (PSOD) that displays messages similar to the following if any changes are made to BufferCache.HardMaxDirty.
2012-02-28T05:30:36.202Z cpu2:4993)@BlueScreen: NOT_REACHED bora/vmkernel/filesystems/caches/bufferCache.c:5817
2012-02-28T05:30:36.202Z cpu2:4993)Code start: 0x418018800000 VMK uptime: 0:00:40:32.172
2012-02-28T05:30:36.204Z cpu2:4993)0x41220e047d18: [0x41801886cd2a]Panic@vmkernel#nover+0xa9 stack: 0x41220e047d50
2012-02-28T05:30:36.206Z cpu2:4993)0x41220e047d48: [0x418018a63020]BC_UpdateConfig@vmkernel#nover+0x307 stack: 0x0
2012-02-28T05:30:36.208Z cpu2:4993)0x41220e047d78: [0x418018820771]ConfigWriteIntegerInternal@vmkernel#nover+0x90 stack: 0x41220e047dc8
2012-02-28T05:30:36.210Z cpu2:4993)0x41220e047dc8: [0x41801882086e]Config_SysInfoSetInt@vmkernel#nover+0x8d stack: 0x41000e713420
2012-02-28T05:30:36.212Z cpu2:4993)0x41220e047e58: [0x418018b53084]VSI_SetInfo@vmkernel#nover+0x17b stack: 0x410001e710c0
2012-02-28T05:30:36.214Z cpu2:4993)0x41220e047ee8: [0x4180189ba32e]UWVMKSyscallUnpackVSI_Set@vmkernel#nover+0x1cd stack: 0x183a70a4
2012-02-28T05:30:36.216Z cpu2:4993)0x41220e047f18: [0x41801898e755]User_UWVMKSyscallHandler@vmkernel#nover+0xa0 stack: 0x4e5b7a48
2012-02-28T05:30:36.218Z cpu2:4993)0x41220e047f28: [0x4180188f1047]gate_entry@vmkernel#nover+0x46 stack: 0x0
- PR 853333: Virtual machines fail to autostart on ESXi 5.0 U1 host assigned with free Hypervisor license. The following message is logged in the hostd logs:
- PR 855177: If you configure the loghost of syslogd incorrectly via esxcli or edit the /etc/vmsyslog.conf file directly followed by syslog reload, syslogd might terminate abruptly. You might notice the following symptoms with this issue:
- Unable to record Syslog
- Unable to run vmsyslogd process
- Unable to run some esxcli commands
For example: esxcli software vib list Got no data from process /usr/lib/vmware/esxcli-software vib.list
- Unable to upgrade ESXi.
- PR 855196: When using CIM intrinsic and extrinsic methods, the response from CIM provider takes much longer time than when compared with executing the same operation on ESXi 5.0.0.
- PR 862428: A CIM client might time out on enumerating VMware_HHRCWrapperSoftwareIdentity in large RAID configurations as the enumeration fails due to the long time it takes for provider initialization.
- PR 863115: Under certain circumstances Logical Unit(LU) on storage controllers claimed by VMW_SATP_LSI plugin might not respond to the plugin issued path evaluation commands within the plugin timeout period of 5 seconds. When two or more vSphere hosts share access to these affected LUs, they might result in path thrashing. This issue is more likely to be seen with storage controllers using the iSCSI protocol.
Note: Before installing this patch please consult your storage vendor to determine the guest operating system I/O timeout value.
- PR 866810: On Dvportgroup, a promiscuous port might not work in promiscuous mode if the DVMirror sessions are reconfigured.
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.