Dell Release Date: 7th Dec 2015 ESXi 5.5 Update 3a 16 OCT 20151180 Build 3116895 Dell Version-A02 This is Dell Customized ESXi5.5 Update 3 (Build 3116895) image with latest drivers included in to the image. Please refer Important Information section for additional drivers included in this release. VMware ESXi 5.5 Update 3a Release Notes ============================================== VMware ESXi 5.5 Update 3a Release Notes VMware ESXi,. 5.5 Update 3a I 6 OCT 20151 Build 3116895 Last updated: 6 OCT 2015 Check for additions and updates to these release notes. What's in the Release Notes The release notes cover the following topics: • Whars New • Earlier Releases of ESXi 5.5 • Internationalization • Compatibility and Installation • Upgrades for This Release • Open Sourca Components for VMware vSphere • Product Support Notices • Patches Contained in this Release • Resolved Issues • Known Issues What's New This release of VMware ESXi contains the following enhancements: • Log Rotation Enablement-Log rotation for vmx files allows you to reduce the log file sizes by specifying the size of each log and the number of previo1 to keep. • Certification of PVSCSI Adapter- PVSCSI adapter is certified for use with MSCS, core clustering and applications including SQL and Exchange. This c1 performance gains when moving from LSI Logic SAS to PVSCSI. • Support for Next Generation Pmce .. ors -In this release, we will continue our support for next generation processors from Intel and AMD. Please see VMware Compatibility Guide for more info. • ESXi Authentication for Active Directory- ESXi is modified to only support AES256-CTS/AES128-CTS/RC4-HMAC encryption for Kerberos communic between ESXi and Active Directory. • Resolved Issues- This release delivers a number of bug fixes that have been documented in the Resolved Issues section. Earlier Releases of ESXi 5.5 Features and known issues of ESXi 5.5 are described in the release notes for each release. Release notes for earlier releases of ESXi 5.5, are: • VMware ESXi 5.5 Update 2 Release Notes • VMware ESXi 5.5 Update 1 Release Notes • VMware vSphere 5.5 Release Notes Internationalization VMware vSphere 5.5 Update 3a is available in the following languages: • English • French • German • Japanese • Korean ht!p:l/pubs.vmware.com/Release_NcXss/eiWsphere/55/Vsphere-esxi-55u3-release-nctas.html 1122 1011512015 VMware ESXi 5.5 Update 3a Release Notes • Simplifl&d Chinese • Traditional Chinese Compatibility and Installation ESXi, vCenter Server, and vSphere Web Client Version Compatibility The VMware Product I nteroperability Matrix provides details about the compatibility of current and earlier versions of VMware vSphere components, includin! VMware vCenter Server, the vSphere Web Client, and optional VMware products. Check the VMware Product lnteroperability Matrix also for information abo1 supported management and backup agents before you install ESXi or vCenter Server. The vSphere Client and the vSphere Web Client are packaged on the vCenter Server ISO. You can install one or both clients by using the VMware vCentern Installer wizard. ESXI, vCenter Server, and VDDK Compatibility Virtual Disk Development Kit {VDDK) 5.5.3 adds support for ESXi 5.5 Update 3 and vCenter Server 5.5 Update 3 releases. For more information about VDDK, see http://www.vmware.com/support/developerlvddk/. ESXI and VIrtual SAN Compatibility Virtual SAN doas not support clusters that are configured with ESXi hosts earlier than 5.5 Update 1. Make sure all hosts in the Virtual SAN cluster are upgrad ESXi 5.5 Update 1 or later, before enabling Virtual SAN. vCenter Server should also be upgraded to 5.5 Update 1 or later. Hardware Compatibility for ESXi To view a list of processors, storage devices, SAN arrays, and 1/0 devices that are compatible with vSphere 5.5 Update 3, use the ESXi 5.5 Update 3 informe the VMware Compatibility Guide. Device Compatibility for ESXi To determine which devices are compatible with ESXi 5.5 Update 3a, use the ESXi 5.5 Update 3 information in the VMware Compatibility Guide. Some devices are deprecated and no longer supported on ESXi 5.5 and later. During the upgrade process, the device driver is installed on the ESXi 5.5.x ho might still function on ESXi 5.5.x, but the device is not supported on ESXi 5.5.x. For a list of devices that have been deprecated and are no longer supported 5.5.x, see the VMware Knowledge Base article Deprecated devices and warnings during ESXi 5.5 upgrade process. Guest Operating System Compatibility for ESXI To determine which guest operating systems are compatible with vSphere 5.5 Update 3a, use the ESXi 5.5 Update 3 information in the VMware Compatibililj Virtual Machine Compatibility for ESXi Virtual machines that are compatible with ESX 3.x and later (hardware version 4) are supported with ESXi 5.5 Update 3. Virtual machines that are compatible ESX 2.x and later (hardware version 3) are not supported. To use such virtual machines on ESXi 5.5 Update 3, upgrade the virtual machine compatibility. Se vSphere Upgrade documentation. vSphere Client Connections to Linked Mode Environments with vCenter Server 5.x vCentar Server 5.5 can exist in linked Mode only with other instances of vCentar Server 5.5. Installation Notes for This Release Read the vSphere Installation and Setup documentation for guidance about installing and configuring ESXi and vCentar Server. Although the installations are straightforward, several subsequent conf~guration steps are essential. Read the following documentation: • Licensing in the vCentar Server and Host Management documentation • Networking in the vSphere Networking documentation • Security in the vSphere Security documentation for information on firewall ports Migrating Third-Party Solutions You cannot direcUy migrate third-party solutions installed on an ESX or ESXi host as part of a host upgrade. Architectural changes between ESXi 5.1 and ES: result in the loss of third-party components and possible system instability. To accomplish such migrations, you can create a custom ISO file with Image Builc information about upgrading your host with third-party customizations, see the vSphere Upgrade documentation. For information about using Image Builder 1 a custom ISO, see the vSphere Installation and Setup documentation. Upgrades and Installations Disallowed for Unsupported CPUs vSphere 5.5.x supports only CPUs with L.AHF and SAHF CPU instruction sets. During an installation or upgrade, the installer checks the compatibility of the h CPU with vSphere 5.5.x. If your host hardware is not compatible, a purple screen appears with a message about incompatibility. You cannot install or upgrad vSphere 5.5.x. Upgrades for This Release For instructions about upgrading vCenter Server and ESX/ESXi hosts, see the vSphere Upgrade documentation. Supported Upgrade Path• for Upgrade to ESXI 5.5 Update 3a: ht!p:l/pubs.vmware.com/Release_NcXss/eiWsphere/55/Vsphere-esxi-55u3-release-nctas.html 1011512015 VMware ESXi 5.5 Update 3a Release Notes Upgrede Deliverebles Supported Upgrede Tools Supported Upgrede Paths to ESXi 5.5 Updllte 3a ESX/ESXI 4.0: ESX/ESXI 4.1: ESXIS.O: ESXI5.1 ESXIS lnclud• lnclud• Includes Includes lnclud• ESX/ESXI 4.0 ESX/ESXI 4.1 ESXI 5.0 Update 1 ESXI5.1 ESXI5 Update 1 Update 1 ESXI 5.0 Update 2 Update 1 Update ESX/ESXI 4.0 ESX/ESXI 4.1 ESXI 5.0 Update 3 ESXI5.1 ESXI5 Update2 Update2 Update2 Update ESX/ESXI 4.0 ESX/ESXI 4.1 Update3 Update3 ESX/ESXI 4.0 Update4 VMware-VMvisor- • VMware vCenter Update Yes Yes Yes Yes Yes Installer- Manager s.s.e.updatee3- • CD Upgrade 311689S.x86_64.iso . Scripted Upgrade • VMware vCenter Update Manager ESXiSS8-28151888l.zip • ESXCLI No No Yes• Yes• Yes • VMware vSphere CLI Using patch definitions VMware vCenter Update downloaded from VMware No No No No Yes portal (online) Manager with patch baseline *Note: Upgrade from ESXi 5.0.x, or ESXi 5.1.x, to ESXi 5.5 Update 3a using - ESXi558-281510081. zip is supported only with ESXCLI. You need to run the software profile update --depot• --profile• command to perform the upgrade. For mora information, see tha ESXi 5. Upgrade Options topic in the vSphere Upgrade guide. Open Source Components for VMware vSphere 5.5 Update 3 The copyright statements and licenses applicable to the open source software components distributed In vSphere 5.5 Update 3 are available at http://www.vmware.com/download/vsphere/open_source.html, on the Open Source tab. You cen also download the source tiles for any GPL, LGPL, or other licenses that require the source code or modifications to source code to be made available for the most recent available release of vSphere. Product Support Notices • vSphere Web Client. Because Linux platforms are no longer supported by Adobe Flash, vSphere Web Client is not supported on the Linux OS. Third pa browsers that add support for Adobe Flash on the Linux desktop OS might continue to function. VMware vcenter server Appliance. In vSphera 5.5, the VMware vCenter server Appliance meets high-govemance compliance standards through the enforcement of the DISA security Technical Information Guidelines (STIG). Before you deploy VMware vCenter Server Appliance, see the VMwere Hard• Virtual Appliance Operations Guida for information about the new security deployment standards and to ensure successful operations. • vCenter Server database. vSphere 5.5 removes support for IBM DB2 as the vCenter server database. • VMware Tools. Beginning with vSphere 5.5, all information about how to install and conf~gure VMware Tools in vSphere is merged with the other vSpher documentation. For information about using VMware Tools in vSphere, see the vSphere documentation. Installing and Configuring VMware Tools is not r to vSphere 5.5 and later. • VMware Tools. Beginning with vSphere 5.5, VMware Tools do not provide ThinPrint features. • vSphere Data Protection. vSphare Data Protection 5.1 is not compatible with vSphere 5.5 because of a change in the way vSphare Web Cient operate! vSphere Data Protection 5.1 users who upgrade to vSphere 5.5 must also update vSphere Data Protection to continue using vSphere Data Protection. Patches Contained in this Release This release contains all bulletins for ESXIIhat were released earlier to the release date of this product. See the VMware Down bad Patches page for more Information about the Individual bulleUns. Patch Release ESXi550-Update03 contains the following individual bulletins: ESXiSS0-201510401-BG: Updates ESXi 5.5 esx-base vib Patch Release ESXi550-Update03 contains the following image profiles: ESXI-5.5.0-20151004001-standard ESXI-5.5.0-20151004001-no-tools For information on patch and update classification, see KB 2014447. Resolved Issues ht!p:l/pubs.vmware.com/Release_NcXss/ei'Wsphere/55/Vsphere-esxi-55u3-release-nctas.html 1011512015 VMware ESXi 5.5 Update 3a Release Notes This section describes resolved issues in this release: • Backup • CIM and API Issues • Miscellaneous Issues • Networking Issues • Security Issues • Server Configuration Issues • Supported Hardware Issues • Storage Issues • Upgrade and Installation Issues • Virtual SAN Issues • vCenter Server and vSphere Web Client Issues • VIrtual Machine Management Issues • VMware HA and Fault Tolerance • vMotion and Storage vMotion Issues • VMware Tools Issues Backup Issues • Attempts to rntore a virtual mach ina might fail with an erTOr Attempts to restore a virtual machine on an ESXi host using vSphere Data Protection might fail and display an error message similar to the following: Unexpected exception received during reconfigure This Issue Is resolved In this release. CIM and API Issues • sp- in syslog when system event log is full and indication suncriptions exist Spew in syslog when System Event Log (SEL) is full and indication subscriptions exist. The following logs are logged in rapidly: sfcb-vmware_raw[xxxxxxxxxx]: Can't get Alert Indication Class. Use default sfcb-vmware_raw[xxxxxxxxxx]: can't get Alert Indication Class. Use default sfcb-vmware_raw[xxxxxxxxxx]: Can't get Alert Indication Class. Use default This issue is resolved in this release. • CIM Indications might fall when you use Auto Deploy to reboot the ESXI hosts If the sfcbd service stops running, the CIM Indications In host proflle cannot be applied successfully. This Issue Is resolved In this release by ensuring that the CIM Indications do not rely on the status of the sfcbd service while applying the host proflle. • Status of some disks might be displayed as UNCONFIGURED GOOD Instead of ONLINE Status of some disks on an ESXi 5.5 host might be displayed as UNCONFIGURED GOOD instead of ONLINE. This issue occurs for LSI controller using tl CIM provider. This issue is resolved in this release. • Load kernel module might tall through CIM Interface The LoadModule command might fail when using the CIM interface client to load the kernel module. An error message similar to the following is display. Access denied by VMkernel access control policy. This issue is resolved in this release. • Monitoring an ESXi 5.5 host with Dell OpenManage might fail due to openwsmand erTOr Monitoring an ESXi 5.5 host with Dell OpenManage might fail due to an openwsmand erTOr. An error message similar to the following might be reported i1 syslog .log file: Failed to map segment from shared object: No space left on device This Issue Is resolved In this release. • Querying hardware status on the vSphara Client might fall with an BITDr Attempts to query the hardware status on the vSphere Client might fail. An erTOr message similar to the following is displayed in the /va r /log/syslog .1~ the ESXi host: TIMEOUT DOING SHARED SOCKET RECV RESULT (1138472) Timeout (or other socket error) waiting for response from provider Header It (16940) Request to provider 111 in process 4 failed. Error:Timeout (or other socket error) waiting for response from provider Dropped response operation details -- nameSpace: root/cimv2, 'lassName: OMC_RawipmiSensor, Type: 0 This issue is resolved in this release. • Monltoltng an ESXI 5.5 hoet with Dell OpanManage might fall due to opanwsmand erTOr Monitoring an ESXi 5.5 host with Dell OpenManage might fail due to an openwsmand erTOr. An error message similar to the following might be reported i1 ht!p:l/pubs.vmware.com/Release_NcXss/eiWsphere/55/Vsphere-esxi-55u3-release-nctas.html 11l11512015 VMware ESXi 5.5 Update 3a Release Notee syslog.log file: Failed to map segment from shared object: No space left on device This issue is resolved in this release. The sfcbd service might stop responding with an anur message The sfcbd service might stop responding and you might find the following error message in the syslog file: spsendReq/spsendMsg failed to send on 7 (-1) Error getting provider context from provider manager: 11 This issue occurs when there is a contention for semaphore between the CIM server and the providers. This issue is resolved in this release. False alanna appear in the Hardware Status tab of the vSphara Client Mer you upgrade Integrated Lights Out (iLO) firmware on HP DL980 G7, false alarms appear in the Hardware Status tab of the vSphere Client. Error me similar to the following might be logged in the /var/log/syslog.log file: sfcb-vmware_raw[nnnnn]: IpmiifruinfoAreaLength: Reading FRU for Bx8 at BxB FAILED cc=8xffffffff sfcb-vmware_raw[nnnnn]: IpmiifcFruChassis: Reading FRU Chassis Info Area length for 0x8 FAILED sfcb-vmware_raw[nnnnn]: IpmiifcFruBoard: Reading FRU Board Info details for Bx8 FAILED cc=Bxffffffff sfcb-vmware_raw[nnnnn]: IpmiifruinfoAreaLength: Reading FRU for 0x8 at 0x70 FAILED cc=8xffffffff sfcb-vmware_raw[nnnnn]: IpmiifcFruProduct: Reading FRU product Info Area length for 0x8 FAILED sfcb-vmware_raw[nnnnn]: IpmiifcSelReadEntry: data length mismatch req=19~resp=3 sfcb-vmware_raw[nnnnn]: IpmiifcSelReadEntry: Entryld mismatch req•8081,resp•8082 sfcb-vmware_raw[nnnnn]: IpmiifcSelReadEntry: Entryld mismatch req=8082,resp=8083 sfcb-vmware_raw[nnnnn]: IpmiifcSelReadEntry: sfcb-vmware_raw[nnnnn]: IpmilfcSelReadEntry: sfcb-vmware_raw[nnnnn]: IpmiifcSelReadEntry: sfcb-vmware_raw[nnnnn]: IpmilfcSelReadEntry: This issue is resolved in this release. Entryld Entryld Entryld Entryld ESXi might send duplicate events to management software mismatch req=8083,resp=8084 mismatch req=8084,resp=BB85 mismatch req=808S,resp=8006 mismatch req•8086,resp•8087 ESXi might send duplicate events to the management software when an Intelligent Platform Management Interface (IPMI) sensor event is triggered on th Host. This issue is resolved in this release. Unable to monitor Hardware Status after ramovlng CIM Indication subscription If the CIM client sands two requests of Delete Instance to the same CIM indication subscription, the sfcb-vmware_int might stop responding due to me contention. You might not be able to monitor the Hardware status with the vCenter Server and ESXi. This issue is resolved in this release. Monitoring an ESXI 5.5 host with Dell OpanManaga might fall due to opanwamand error Monitoring an ESXi 5.5 host with Dell OpanManage might fail respond due to openwsmand error. Ar1 error message similar to the following might be rape Failed to map segment from shared object: No space left on device This issue is resolved in this release. CIM client might display an error due to multiple enumeration When you execute multiple enumerate queries on VMware Bhemet port class using the CBEnumlnstances method, servers running on an ESXi 5.5 migl an error message similar to the following: CIM error: enumlnstances Class not found This issue occurs when the management software fails to rebieve information provided by VMware_EthernetPort()class. When the issue occurs, query 01 memstats might display the following error message: MemStatsTraverseGroups: VSI_GetinstanceListAlloc failure: Not found. This issue is resolve in this release. Unable to monitor Hardware Status on an ESXi host Ar1 ESXi host might report an error in the Hardware Status tab due to the unresponsive hardware monitoring service (sfcbd). Ar1 error similar to the follow written to syslog.log: sfcb-hhrc[5149688]: spGetMsg receiving from 65 5149688-ll Resource temporarily unavailable sfcb-hhrc[5149688]: rcvMsg receiving from 65 5149688-11 Resource temporarily unavailable sfcb-hhrc[5149688]: Timeout or other socket error sfcb-LSIESG_SMIS13_HHR[6864161]: spGetMsg receiving from 51 6864161-ll Resource temporarily unavailable sfcb-LSIESG_SMIS13_HHR[6864161]: rcvMsg receiving from 51 6864161-11 Resource temporarily unavailable sfcb-LSIESG_SMIS13_HHR[6864161]: Timeout or other socket error sfcb-kmoduleprovider[6064189]: spGetMsg receiving from 57 6864189-11 Resource temporarily unavailable sfcb-kmoduleprovider[6064189]: rcvMsg receiving from 57 6864189-11 Resource temporarily unavailable sfcb-kmoduleprovider[6064189]: Timeout or other socket error ht!pJ/pubs.vmware.com/Release_Nctss/entvsphere/551Vsphere-esxi-56u3-releese-notes.htrnl 5122 11l11512015 VMware ESXi 5.5 Update 3a Release Notee The syslog below in debug level indicates that an invalid data of Ox3c is sent by IPMI when the expected data is Ox01. sfcb-vmware_raw[35704]: IpmiifcRhFruinv: fru.header.version: 8x3c This issue occurs when sfcb-vmware_raw provider receives invalid data from the Intelligent Platform Management Interface (I PM I) tool while reading the Replaceable Unit (FRU) inventory data. This issue is resolved in this release. Miscellaneous Issues Cloning CBT -enabled virtual machine tamplataa from ESXI boats might fall Attempt to clone CBT -enabled virtual machines templates simultaneously from two different ESXI5.5 hosts might fall. An error message similar to the folli displayed: Failed to open VM_template.vmdk': Could not open/create change tracking file (2108). This issue is resolved in this release. Unable to log Into ESXI host with Active Directory credential& Attempts to login to an ESXI host might fall after the host successfully joins an Active Directory. This occurs when a user from one domain attempts to jolr another trusted domain, which Is not present In the ESXI dlent site. An error similar to the following Is written to sys .log/netlogon .log file: netlogond[17229]: [LWNetDnsQueryWithBuffer() /build/mts/release/bora-1028347/likewise/esxi-esxi/src/linux/netlogon/utils/lwne· dns.c:1185] DNS lookup for '_ldap._tcp.' failed with errno 01 h_errno = 1 This issue is resolved in this release. Update to the cURL library cURL fails to resolve localhost when 1Pv6 is disabled. An error message similar to the following is displayed: error: enumlnstances Failed initialization This issue is resolved in this release. Networking Issues ESXi hosts with the virtual machines having e1000 or e1000a vNIC driver might fail with a purple screen ESXi hosts with the virtual machines having e1 000 or e1 OOOe vNIC driver might fail with a purple screen when you enable TCP segmentation Offload (TS Error messages similar to the following might be written to the log files: cpu7:nnnnnn)Code start: Bxnnnnnnnnnnnn VMK uptime: 9:21:12:17.991 cpu7:nnnnnn)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]E1000TxTSOSend@Ymkernel#nover+0x65b stack: exnnnnnnnnnn cpu7:nnnnnn)0xnnnnnnnnnnnn:[8xnnnnnnnnnnnn]E1000PollTxRins@Ymkernel#nover+0x18ab stack: exnnnnnnnnnnnn cpu7:nnnnnn)8xnnnnnnnnnnnn:[8xnnnnnnnnnnnn]E1000DevAsyncTx@vmkernel#nover+Bxa2 stack: 8xnnnnnnnnnnnn cpu7:nnnnnn)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]NetWorldletPerVMCB@vmkernel#nover+0xae stack: exnnnnnnnnnnnn cpu7:nnnnnn)axnnnnnnnnnnnn:[axnnnnnnnnnnnn]WOrldletProcessQueue@vmkernel#nover+8x488 stack: Bxnnnnnnnnnnnn cpu7:nnnnnn)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]WorldletBHHandler@vmkernel#nover+0x60 stack: exnnnnnnnnnnnnnnn cpu7:nnnnnn)0xnnnnnnnnnnnn:[8xnnnnnnnnnnnn]BH_Chec~kernel#nover+Bxl8S stack: 0xnnnnnnnnnnnn This issue is resolved in this release. ESXi rasponds to unnecessary Internet Control Message Protocol request types The ESXi host might respond to unnecessary Internet Control Message Protocol (ICMP) request types. This issue is resolved in this release. ESXI hoatd might fall when perfonnlng storage device raacan operation• When you perform storage device rescan operaUons, the hostd might fall as muiUple threads attempt to modify the same object. You might see error me1 similar to the following In the vmkwarning.log file: cpu43:nnnnnnn)ALERT: hostd detected to be non-responsive cpu20:nnnnnnn)ALERT: hostd detected to be non-responsive This issue is resolved in this release. Log spew Ia observed when ESXI host Ia added In vCentar server When you add an ESXi host in vCenter server and create a VMkemel interface for vMotion, you will see the following message displayed in quick succes1 spew) in the hostd .log file: Failed to find vds Id for portset vSwitche This issue is resolved in this release. Microsoft Windows Deployment Services (WDS) might fail to PXE boot virtual machines that use the VMXNET3 network adapter Attempts to PXE boot virtual machines that use the VMXNET3 network adapter by using the Microsoft Windows Deployment Services (WDS) might fail wi messages similar to the following: Windows failed to start. A recent hardware or software change might be the cause. To fix the problem: 1. Insert your Windows installation disc and restart your computer. 2. Choose your language setting~ and then click Next. ht!pJ/pubs.vmware.com/Releese_Nctss/entvsphere/551Vsphere-esxi-56u3-rel....,.notes.htrnl 6122 11l11512015 VMware ESXi 5.5 Update 3a Release Notee 3. Click Repair your computer. If you do not have the disc~ contact your system administrator or computer manufacturer for assistance. Status: exceeeeee1 Info: The boot selection failed because a required device is inaccessible. This Issue Is resolved In this release. Enable the configuration of Rx Ringfl2 to solve the Rx Ring#2 out of memory and packet drops on the raceivar side issues A Linux virtual machine enabled with Large Receive Offload (LRO) functionality on VMXNET3 device might experience packet drops on the receiver side the Rx Ring #2 runs out of memory, since the size of Rx Ring#2 is unable to be configured originally. This issue is resolved in this release. Purple diagnostic screen might be displayed when ualng DvFIIterwlth a NetQueua supported uplink An ESXI server might experience a purple dlagnosuc screen when using DvFIIter with a NetQueue supported uplink connected to a vSwltch or a vSphere Distributed SWitch (VDS). The ESXI host might report a backtrace similar to the following: pcpu:22 world:4118 name:nidle22n (IS) pcpu :23 world:2592367 name: nvmml :518274-AAG" (V) @BlueScreen: Spin count exceeded (AP) - possible deadlock Code start: Bxnnnnnnnnnnnn VMK uptime: 57:99:18:15.779 Bxnnnnnnnnnnnn:[Bxnnnnnnnnnnnn]Panic@vmkernel#nover+Bxnn stack: Bxnnnnnnnnnnnn exnnnnnnnnnnnn:[exnnnnnnnnnnnn]SP_Waitlock@vmkernel#nover+Oxnnn stack: exnnnnnnnnnnnn exnnnnnnnnnnnn:[exnnnnnnnnnnnn]Net5chedFIFOinput@Mmkernel#nover+exnnn stack: exe exnnnnnnnnnnnn:[exnnnnnnnnnnnn]NetSchedinput@Ymkernel#nover+Bxnnn stack: Bxnnnnnnnnnnnn exnnnnnnnnnnnn:[Bxnnnnnnnnnnnn]IOChain_Resume@vmkernel#nover+Oxnnn stack: exnnnnnnnnnnnn exnnnnnnnnnnnn:[Oxnnnnnnnnnnnn]PortOutput@vmkernel#nover+Oxnn stack: Bxnn This issue is resolved in this release. ESXI host falls with purple diagnostic scn~en when the Netflow faatun~ls deactivated An ESXI host might fall with a PF exception 14 purple diagnostic screen when the Netflow feature of vSphere Distributed Switch gets deactivated. The Iss occurs due to a timer synchronization problem. This Issue Is resolved In this release. Changing the network scheduler to SFQ during heavy 110 might rasult in an unracoverable t111.nsmission When heavy 1/0 load is in progress, the SFQ Network scheduler might reset the physical NIC when switching the network schedulers. This might cause a unrecoverable transmission where no packets are transmitted to the driver. This issue is resolved in this release. vmkplng command with Jumbo Frames might fall The vmkplng command with Jumbo Frames might fall after one vmknlc MTU Is changed amongst many In the same switch. An error message similar to 1 following Is displayed: sendto() failed (Message too long) This issue is resolved in this release. ESXi firewall might reject the servicea that use port 0-65535 as service port The Virtual Serial Port Concentrator (vSPC) or NFS dient service might not function on the ESXi platform. This happens when there is a different ruleset 1 which allows port 0-65535, as a result of enabling sequence. This results in the vSPC or NFS Client related packets to be dropped unexpectedly even if tl allowed IP on corresponding ruleset is specified. This issue is resolved in this release. 1Pv6 RA does not function as expected when tagging 802.1q with VMXNET3 adapters 1Pv6 Router Advertisements (RA) does not function as expected when tagging 802.1q with VMXNET3 adapters in an Linux virtual machine as the 1Pv6 RJ address intended for the VI..AN interface is delivered to the base interface. This issue is resolved in this release. ESXi host might lose network connectivity An ESXi host might lose network connectivity and experience stability issues when multiple error messages similar to the following are logged in: WARNING: Heartbeat: 785: PCPU 63 didn't have a heartbeat for 7 seconds; *may* be locked up. This issue is resolved in this release. Network connectivity lost when applying host profile during Auto Deploy When applying host profile during Auto Deploy, you might lose network connectivity because the VXLAN Tunnel Endpoint {VTEP) NIC gets tagged as management vmknic. This issue is resolved in this release. Security Issues • Update to the llbxml2 llb111.ry ht!pJ/pubs.vmware.com/Release_Nctss/entvsphere/55/Vsphere-esxi-56u3-releese-notes.htrnl 7122 1011512015 VMware ESXi 5.5 Update 3a Release Notes The ESXi userworid libxrnl2 library is updated to verion 2.9.2. • Update to the ESXI usarwoltd OpanSSL library The ESXi userworld OpanSSL library is updated to version 1.0.1m. • Update to the libPNG library The libPNG library is updated to libpng-1.6.16. Server Configuration Issues • Serial over LAN Console Redirection might not function property A PCie serial port redirection card might not function properly when connected to an Industry Standard Architecture {ISA) Interrupt Request {IRQ) (0-15 decimals) on an Advanced Programmable Interrupt Controller {APIC) as it is unable have its interrupts received by the CPU. To allow these and other PC devices connected to ISA IRQs to function, VMkernel will now allow level-triggered interrupts on ISA IRQs. This issue is resolved in this release. • &xtop might Incorrectly display the CPU utilization at 1 00% The PCPU UTIUCORE UTIL in esxtop utility incorrectly displays CPU utilization at 100% if you have the PcpuMigrateldlePcpus set at D. This issue is resolved in this release. • Unknown(1) status reported when querying Fiber Channel Host Bus Adapters Mer you upgrade the ESXI host from ESXI 5.1 to 5.5 and Import the latest MIB module, the third-party monitoring software returns "unknown( 1 )" status ~ querying Fiber Channel (FC) Host Bus Adapters (HBA). This Issue Is resolved In this release. • Host gataWlly delated and compliance failures might occur when existing ESXI host profile re-applied to stataful ESXI host When an existing ESXi host profile is applied to a newly installed ESXi 5.5 host, the profile compliance status might show as noncompliant. This happens the host profile is created from hosts with VXLAN interface configured, the test for compliance on hosts with the previously created host profile might fail. error message similar to the following is displayed: IP route configuration doesn't match the specification This issue is resolved in this release. • Purple diagnostic screen with Page Fault exception displayed In a nested ESXI environment In a nested ESXi environment, implementation of CpuSchedAfterSwitc h () results in a race condition in the scheduler coda and a purple diagnostic sere Page Fault exception Is displayed. This issue is resolved in this release. • ISCSIInltlator nama allowed when enabling software ISCSI using esxcll You can now specify an iSCSI initiator name to tha esxcli iscsi software set command. • VIrtual machine might not display a warning message when the CPU Is not fully reserved When you create a virtual machine with sched. cpu.latencysensitivity set to high and power it on, the exclusive affinity for the vCPUs might not get e if the VM does not have a full CPU reservation. In earlier releases, the VM did not display a warning message when the CPU Is not fully reserved. For mora Information, see Knowledge Base article 208 This Issue Is resolved In this release. • SNMPD might start automatically after ESXI host upgrade The SNMPD might start automatically after you upgrade the ESXi host to 5.5 Update 2. This issue is resolved in this release. • Host profiles become non-compliant with simple change to SNMP syscontact or syslocation Host Profiles become non-compliant with a simple change to SNM P syscontact or syslocation. The issue occurs as the SNMP host profile plug in applies c single value to all hosts attached to the host profile. An error message similar to the following might be displayed: SNMP Agent Configuration differs This issue is resolved in this release by enabling per-host value settings for certain parameters like syslocation, syscontact, v3targets,v3users and enginE • Attempta to create a FIFO and write data on it might reault in a purple diagnostic screan When you create a FIFO and attempt to write data to the ltmp/dpafifo, a purple diagnostic screen might displayed under certain conditions. This issue is resolved in this release. • Attempts to reboot Windows 8 and Windows 2012 aerveron ESXI host virtual machlnea might fall Mer you reboot, the Windows 8 and Windows 2012 Server virtual machines might become unresponsive when the Microsoft Windows boot splash scree appears. For more information refer, Knowledge Base article 2092807. This issue is resolved in this release. • Attempts to reboot Windows 8 and Windows 2012 server on ESXi host virtual machines might fail When you set the CPU limit of a uni-processor virtual machine, the overall ESXi utilization might dea-ease due to a defect in the ESXi scheduler. This hap when the ESXi scheduler considers the cpu-limited VMs as runnable (when they were not running) while making cpu-load estimations. Hence leading to i load balancing decision. For details, see Knowledge Base article 2098897. ht!p:l/pubs.vmware.com/Release_NcXss/eiWsphare/55/Vsphere-esxi-55u3-release-nctas.html 11l11512015 VMware ESXi 5.5 Update 3a Release Notee This issue is resolved in this release. Supported Hardware Issues Power usage and power cap value missing in asxtop command On Lenovo systems, the value of power usage and power cap is not available in the esxtop command. This issue is resolved in this release. Storage Issues During an High Availability falloverora host crash, the .vswp flies of powered ON VMs on that host might be left behind on the storage Durtng a High Availability fallover or host crash, the • vswp flies of powered ON virtual machines on that host might be left behind on the storage. When m such failovers or crashes occur, the storage capacity might become full. This issue is resolved in this release. False PE change message might be displayed In the VMkamellog fila when you reacan a VMFS dataatora with multiple extent& When you rescan a VMFS datastore with multiple extents, the following log message might be written In the VMkemellog even without any Issues from s connectivity: Number of PEs for volume changed from 3 to 1. A VMFS volume rescan may be needed to use this volume. This issue is resolved in this release. During transient error conditions, 110 to a device might repeatedly fall and not fallovar to an alternate working path During transient error conditions like BUS BUSY, QFULL, HOST ABORTS, HOST RETRY and so on, you might repeatedly attempt commands on current and do not fallover to another path even after a reasonable amount of Ume. This Issue Is resolved In this release. During occurrence of such transient errors, If the path Is busy after a couple of retries, the path state Is now change DEAD. M a result, a fallover Is triggered and an alternate working path to the device Is used to send 1/0s. During an High Availability fallover or a host cmsh, the .vswp flies of powered ON VMs on that host might be left behind on the stomga During a High Availability failover or host aash, the • vswp files of powered ON virtual machines on that host might be left behind on the storage. When m such fallovers or crashes occur, the storage capacity might become full. This Issue Is resolved In this release. Attempts to gat block map of an offline storage might cause the hostel service to crash The hostd service might fail on an ESXi 5.x host when there is an acquireLeaseExt API execution attempt on a snapshot disk which goes offline. This sr disk may be on an extent which has gone offline. The API caller may be a third-party backup solution. An error message similar to the following is display vmkernel.log: cpu4:4739)LVM: 11729: Some trailing extents missing (498. 696). This issue is resolved in this release. ESXI 5.5 host might stop ntSpondlng wHh a purple diagnostic screen during collection of vm-support log bundle When any inbox or third-party drivers do not have their SCSI transport-specific interfaces defined, the ESXi host might stop responding and display a pur1 diagnostic screen. The issue occurs during collection of vrn-support log bundles or when you run 1/0 Device Management (lOOM) Command-Line lnterfa (CLI) such as: o esxcli storage san sas list o esxcli storage san sas stats get This Issue Is resolved In this release. Attempts to expand VMFS volumes beyond 18 TB might not succeed In certain scenarios An ESXi host might fail when you attempt to expand a VMFS5 datastore beyond 16 TB. Error messages similar to the following is written to the vmkernel file: cpu38:34276)LVM: 2997: [naa.699999e99d289999992809c9ee919999:1] Device expanded (actual size 61169331231 blocks. stored size 39589164575 blocks) cpu38:34276)LVM: 2997: [naa.699999e99d289999992809c909919999:1] Device expanded (actual size 61169331231 blocks. stored size 39589164575 blocks) cpu47:34276)LVM: 11172: LVM device naa.699009e99d28988988280Bc800919988:1 successfully expanded (new size: 31314889599272) cpu47:34276)Vol3: 661: Unable to register file system ds92 for APD timeout notifications: Already exists cpu47:34276)LVM: 7877: Using all available space (15657383277568). cpu7:34276)LVM: 7785: Error adding space (0) on device naa.690009e99d280090082809c899819880:1 to volume 52f05483-52ea4568-ce91 991b9e9cd9f0: No space left on device cpu7:34276)LVM: 5424: PE grafting failed for dev naa.699899e99d289999992899c&e9919999:1 (opened: t). val 52f95483-52ea4568-cel 901b0e9cd9f0: Limit exceeded cpu7:34276)LVM: 7133: Device scan failed for : Limit exceeded cpu7:34276)LVM: 7805: LVMProbeDevice failed for device naa.690009e99d288098002809c099019000:1: Limit exceeded cpu32:38963)<3>atal.89: bad CDB len=l6. scsi_op=9x9e. max=l2 cpu38:38063)LVM: 5424: PE grafting failed for dev naa.609880e88d289980982888c980918998:1 (opened: t), val 52f85483-52ea4568-C1 901b0e9cd9f0: Limit exceeded ht!pJ/pubs.vmware.com/Release_Nctss/entvsphere/55/Vsphere-esxi-56u3-releese-notes.htrnl 11l11512015 VMware ESXi 5.5 Update 3a Release Notee cpu3B:38B63)LVM: 7133: Device scan failed for : Limit exceeded This issue is resolved in this release. ESXi host might fail with a purple diagnostic screen when multiple vSCSI fiHers are aHached to a VM disk An ESXi 5.5 host might fail with a purple diagnostic saeen similar to the following when multiple vSCSI filters are attached to a VM disk. cpu24:1B3492 opiD•nnnnnnnn)@BlueScreen: #PF Exception 14 in world 1B3492:hostd-worker IP Bxnnnnnnnnnnnn addr Bx3B PTEs:axnnnnnnnnnn;Bxnnnnnnnnnn;exe; cpu24:103492 opiD=nnnnnnnn)Code start: Bxnnnnnnnnnnnn VMK uptime: 21:06:32:38.296 cpu24:1B3492 opiD=nnnnnnnn)Bxnnnnnnnnnnnn:[Bxnnnnnnnnnnnn]VSCSIFilter_GetFilterPrivateData@vmkernel#nover+Bxl stack: Bx4136c7t cpu24:103492 opiD=nnnnnnnn)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]VSCSIFilter_IssuelnternalCommand@vmkernel#nover+0xc3 stack: 0x41096: cpu24:103492 opiD=nnnnnnnn)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]CBRC_FileSyncRead@kNone>#+0xb1 stack: exe cpu24:103492 opiD=nnnnnnnn)0xnnnnnnnnnnnn:[exnnnnnnnnnnnn]CBRC_DigestRecompute@kNone>#+0x291 stack: 0x1391 cpu24:103492 opiD•nnnnnnnn)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]CBRC_FilterDigestRecompute@#+0x36 stack: 0x20 cpu24:103492 opiD=nnnnnnnn)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]VSI_Setlnfo@vmkernel#nover+0x322 stack: 0x411424b18120 cpu24:103492 opiD=nnnnnnnn)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]UWVMKSyscallUnpackVSI_Set@#+0xef stack: 0x4124511ldfl0 cpu24:103492 opiD=nnnnnnnn)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]User_UWVMKSyscallHandlen@#+Bx243 stack: 0x4124511ldf20 cpu24:103492 opiD=nnnnnnnn)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]User_UWVMKSyscallHandlen@Mmkernel#nover+0xld stack: 0x275c3918 cpu24:103492 opiD=nnnnnnnn)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]gate_entry@Ymkernel#nover+0x64 stack: exe This issue is resolved in this release. ESXi host stope responding and Iosee connection to vCenterServer during storage hiccups on Non-ATS VMFS dataatorea An ESXi host might stop responding and the virtual machines become inaccessible. Also, the ESXi host might lose connection to vCenter Server due to a deadlock during storage hicuups on Non-ATS VMFS datastores. This issue is resolved in this release. ESXI host gate raglaterad with an Incorrect IQN on a target management aoftwara Unisphere Storage Management software registers the given initiator IQN when software iSCSI is first enabled. During stateless boot, the registered IQN not change with the name defined in host profile. You are required to manually remove the initiators from the array and add them again under the new IC This issue is resolved by adding a new parameter to the software iSCSI enable command so that Unisphere registers the initiator under the name detinet host profile. The command line to set the IQN during software iSCSI enablement is: esxcli iscsi software set --enabled=true --name iqn,xyz vSphera Replication sync might fall due to change In source dataatora nama If you rename a datastore on which replication source virtual machines are running, replication sync operations for these virtual machines fail with an errc message similar to the following: VRM Server runtime error. Please check the documentation for any troubleshooting information. The detailed exception is: 'Invalid datastore format '' This issue is resolved in this release. Attempts to unmount NFS Datastora might fail Attempts to unmount NFS Datastore might fail as the NFS lOs could be stuck due to connectivity issues during NFS LOCK LOST errors. You will see an t message similar to the following: cpu23:xxxxx opiD=xxxxxabf)WARNING: NFS: 1985: datastorel has open files~ cannot be unmounted This issue is resolved in this release. Upgrade and Installation Issues Error message observed on the boot scraen when ESXI5.5 host boots from vSphere Auto Deploy Statelaaa Caching An error message similar to the following with traceback& Is observed on the boot screen when ESXI5.5 host boots from Auto Deploy Stateless Caching. error Is due to an unexpected short length message of less than four characters In the syslog network. py script. IndexError: string index out of range This issue is resolved in this release. Attempts to install or upgrade VMwara Tools on a Solaria 10 Update 3 virtual machine might fail Attempts to install or upgrade VMware Tools on a Solaris 10 Update 3 virtual machine might fail with the following error message: Detected X version 6.9 Could not read /usr/lib/vmware-tools/configurator/XOrg/7.0/vmwlegacy_drv.so Execution aborted. This issue occurs if the vrnware-config-tools. pl script copies the vrnwlegacy_drv. so file, which should not be used in Xorg 6.9. Keyboard layout option for DCUI and host profile user interface might be incorrectly displayed as Czechoslovakian The keyboard layout option for the Direct Console User Interface (DCUI) and host profile user interface might incorrectly appear as Czechoslovakian. Thi is displayed during ESXi installation and also in the DCUI after installation. This issue is resolved in this release by renaming the keyboard layout option to Czech. Option to retain toola.conf file available by default When you upgrade the Vmware Tools in 64-bit Windows guest operating system, the tools. conf file gets removed automatically. The tools. conf file "' ht!pJ/pubs.vmware.com/Release_Nctss/entvsphere/55/Vsphere-esxi-56u3-releese-notes.htrnl 11l122 1011512015 VMware ESXi 5.5 Update 3a Release Notes retained by default from ESXi 5.5 Update 3 release onwards. • Guut Operating System might fall on raboot after Install, upgrade, or unlnstall of VMwara Tools When you powar off a virtual machine immediately after an install, upgrade or uninstall of VMwara Tools in a Linux environment (RHEL or Cant OS 6), th1 OS might fail during the next reboot due to corrupted RAM DISK image file. The guest OS reports an error similar to the following: RAMDISK: incomplete write {31522 l= 32768) write error Kernel panic - not syncing : VFS: unable to mount root fs on unknown-block(B,B) This release resolves the complete creation of the lnltremfs tlle creaUon during an Install, upgrade or unlnstall of VMware Tools. Guest OS with corrupted RAM DISK image file can be rescued to complete boot state. For more information, see Knowledge Base article 2086520. This issue is resolved in this release. • Applying host profile with stateless caching enablltd on atatelaas ESXI host might take a long time to complete Applying host profile on stateless ESXi host with large number of storage LUNs might take long lima to reboot when you enable stateless caching with tht ftrst disk argument. This happens when you manually apply host proftle or during the reboot of the host. This issue is resolved in this release. • VIB atage operation might cauae VIB Installation or conflgu ration change to be lost after an ESXI hoat raboot When soma VIBs are installed on the system, asxupdata constructs a new image in /altbootbank and changes the /altbootbank boot.cfg bootstata updated. When a live lnstallable VIB Is Installed, the system saves the conftguraUon change to I al tbootba nk. The stage operation deletes the contents < /al tbootban k unless you perform a remediate operation after the stage operation. The VI B installation might be lost if you reboot the host after a stage operation. This Issue Is resolved In this release. Virtual SAN Issues • VIrtual SAN cluster check might fall due to unexpected network partition lng In the cluater Virtual SAN cluster check might fail due to an unexpected network partitioning where the IGMP v3 query is not reported if the system is in V2 mode. This issue is resolved in this release. • VIrtual SAN on high latency dlska might causa thelnpuUOutput backlogs and the cluatarto become unraaponalve Virtual SAN does not gracefully handle extremely high latency disks that are about to die. Such a dying disk might causa lnput!Output backlogs and the V SAN cluster nodes might become unresponsive in the vCentar Server. This issue is resolved in this release with a new feature, Dying Disk Handling (DOH) which provides latency monitoring framework in the kernel, a daamo1 detect high latency periods, and a mechanism to unmount individual disks and diskgroups. • Improvement in Virtual SAN raaynchronization operation There might be a situation where the Virtual SAN component resynchronizalion operation might stall or become very slow. This release introduces the component-based congestion to improve the resynchronization operation and the virtual SAN cluster stability. vCenter Server and vSphere Web Client Issues • The Summary tab might display Incorrect valuaa for provisioned space valuea of virtual mach lnaa and NFS or NAS Dataatoraa on VAAJ a nab I hosts When a virtual disk with Thick Provision Lazy zeroed formal is created on a VAAl supported NAS in a VAAl enabled ESXi host, the provisioned space for 1 corresponding virtual machine and datastore might be displayed incorrectly. This issue is resolved in this release. Virtual Machine Management Issues • Attempta to add USB device through vSphera Client or the vSphera Web Client might fall Attempts to add USB device(s) through vSphera Client and vSphere Web Client might fail if Intel USB 3.0 driver is used. This issue is resolved in this release. • Taking quiesce snapshot of a virtual machine might result in the MOB value of currantSnapshot field to be unset After you create a quiesce snapshot and browse through the Managed Object Browser (MOB) of the virtual machine, the MOB value of currentSnapshot observed to be unset. To view the currentSnapshol, you can navigate to Content-> root folder-> datacenter-> vmFolder -> vmname ->snapshot-> currentSnaphot. This issue is resolved in this release. • Multiple opiD tagging log masaagaa ara rapidly logged In the VMkamellog The helper world opiD tagging generates a lot of log massages that are logged rapidly In the VMkemallog filling II up. Logs similar to the following are lo! the VMkernellog: cpu16:nnnnn)World: nnnnn: VC opiD hostd-60f4 maps to vmkernel opiD nnnnnnnncpu16:nnnnn)World: nnnnn: VC opiD HB-host-nnninnnnnnnnnn- nn maps to vmkernel opiD nnnnnnnncpuB:nnnnn)World: nnnnn: VC opiD SWI-nnnnnnnn maps to vmkernel opiD nnnnnnnn cpu14:nnnnn)World: nnnnn: VC opiD hostd-nnnn maps to vmkernel opiD nnnnnnnncpu22:nnnnn)World: nnnnn: VC opiD hostd-nnnn maps vmkernel opiD nnnnnnnn cpu14:nnnnn)World: nnnnn: vc opiD hostd-nnnn maps to vmkernel opiD nnnnnnnn cpu14:nnnnn)World: nnnnn: VI hostd-nnnn maps to vmkernel opiD nnnnnnnncpu4:nnnnn)Wbrld: nnnnn: VC opiD hostd-nnnn maps to vmkernel opiD nnnnnnnn This issue is resolved in this release. ht!p:l/pubs.vmware.com/Release_NcXss/erVV5phere/55/Vsphere-esxi-55u3-release-nctas.html 11122 1011512015 VMware ESXi 5.5 Update 3a Release Notes • Support for USB 3.0 Support for USB 3.0 has bean added in this release, currently only for Apple Mac Pro. High Availability and Fault Tolerance Issues • In an environment with Nutanix NFS storage, the secondary FT virtual machine fails to lake over when the primary FT virtual machine is down (KB 2096: vMotlon and Storage vMotlon Issues • Unabla to perform Fut Suspend and Reaume or Storage vMotion on praallocatad virtual machinaa When you perform Fast Suspend and Resume (FSR) or storage vMotion on preallocated virtual machines, the operation might fail as the reservation val fails during reservation transfer from the source to the destination virtual machine. This issue is resolved in this release. • Storage vMotlon falls on a virtual machine Performing a storage vMollon on a virtual machine might fall If you have configured the local host swap and sat the value of the checkpoint. cptConfigr the VMX file. An error message similar to the following might be displayed: xxxx-xx-xxT88:xx:xx.888ZI vmxl 1128: VMXVmdbVMVmxMigrateGetParam: type: 2 srcip=<127.8.8.1> dstlp=<127.8.8.1> mid=xxxxxxxxx~ uuid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx priority=none checksumMemory=no maxDowntime=0 encrypted=& resumeDuringPagein=no latencyAware=no diskOpFile= xxxx-xx-xxT&e:xx:xx.812ZI vmxl 1120: VMXVmdb_SetMigrationHostlogState: hostlog state transits to failure for migrate 'to' mid xxxxxxxxxxxxxxxx This issue is resolved in this release. • Changed Block Tracking (CBT) Is reset for virtual ROM disks dultng cold migration Cold migration between different datastores does not support CBT reset for the virtual Raw Device Mapping (ROM) disks. This issue is resolved in this release. VMware Tools Issues • Attempts to upgrade VMwara Tools on a Windows 2000 virtual machine might fall Attempts to upgrade VMware Tools on a Windows 2000 virtual machine might fail with an error massage similar to the following written to the vmmsi .log Invoking remote custom action. DLL: C:\WINNT\Installer\MSI12.tmp, Entrypoint: VMRun VM_CacheHod. Return value 3. PROPERTY CHANGE: Deleting RESUME property. Its current value is '1'. INSTALL. Return value 3. This issue is resolved in this release. • Some ofthe drivens might not worll: as expected on Solaris11 virtual machine On an ESXi 5.5 host, some of the drivers installed on Solaris 11 guest operating system might be from Solaris 1 0. As a result, the drivers might not worll: ; expected. This issue is resolved in this release. • Attempts to configure VMware Tools with new kemal might truncate the dltver nat In add_drtvera entry When you attempt to configure VMware Tools wtth new kernel using the /usr/bin/vmware-config-tools .pl -k scrtpt after the ke been updated with Dracut, the driver list in add_drivers entry of /etc/dracut.conf.d/vmware-tools.conf file gets truncated. This issue occurs when VMware Tools are upstreamed in the kernel. This issue is resolved in this release. • Unable to open telnet on Windows 8 or Windows Sarver 2012 guest operating system after installing VMwara Tools After installing VMware Tools on Windows 8 or Windows Server 2012 guest operating system, attempts to open telnet using the start talnat:/lxx.xx.xx.x: command fails with the following error message Make sure the virtual machine's configuration allows the guest to open host applications This Issue Is resolved In this release. • Guaat operating system avant viewardiaplays warning massages after you install VMwara Tools After you install VMware Tools, if you attempt to do a RDP to a Windows virtual machine, some of the plug ins might display a warning message in the Wi1 event log. The warning massage indicates the failure to sand remota procedure calls to the host. This issue is resolved in this release. • VMware Toole service might fall on a Llnux virtual machine dultng shutdown On a Llnux virtual machine, the VMwara Tools service. vmtoolsd, might fall when you shut down the guest operating system. This issue is resolved in this release. • VMware Toole might fail to automatically upgrade during the firat powar-on operation of the virtual machine When a virtual machine is deployed or cloned with guest customization and the VMwara Tools Upgrade Policy is set to allow the virtual machine to autorr upgrade VMware Tools at next power-on. VMwara Tools might fail to automatically upgrade during the first power-on operation of the virtual machine. ht!p:l/pubs.vmware.com/Release_NcXss/eiWsphere/55/Vsphere-esxi-55u3-release-nctas.html 12122 1011512015 VMware ESXi 5.5 Update 3a Release Notes This issue is resolved in this release. • Qulesclng operations might rat~ult In e Windows virtual machine to panic Attempts to perfonn a quiescad snapshot on a virtual machine running Microsoft Windows 2008 or later might fail and the VM might panic with a blue sen error message similar to the following: A problem has been detected and Windows has been shut down to prevent damage to your computer. If this is the first time you'• seen this Stop error screen restart your computer. If this screen appears again, follow these steps: Disable or uninstall any anti-virus, disk defragmentation or backup utilities. Check your hard drive configuration, and check any updated drivers. Run CHKDSK /F to check for hard drive corruption, and then restart your computer. For more information, see Knowledge Base article 2115997. This issue is resolved in this release. • Virtual machine might fail to raspond after a snapshot operation on a Linux VM When you attempt to create a quiesced snapshot of a Linux virtual machine, the VM might fail after the snapshot operetion and require a reboot. Error messages similar to the following are written to VIIIWare .log file: TZI vmxl 1120: SnapshotVMXTakeSnapshotComplete: done with snapshot 'smvi_UUID': e TZI vmxl 1120: SnapshotVMXTakeSnapshotComplete: Snapshot e failed: Failed to quiesce the virtual machine (49). TZI vmxl 1120: GuestRpcSendTimedOut: message to toolbox timed out. TZI vmxl 1120: Vix: [18631 guestcommands.c:1926]: Error VIX_E_TOOLS_NOT_RUNNING in MAutomationTranslateGuestRpcError(): VMware Tools are not running in the guest For further details, see Knowledge Base article 2116120 This issue is resolved in this release. • New Attempts to perfonn snapshot consolidation might fall with the error: Unexpected signal: 11 Snapshot consolidation or deletion results in the virtual machines running on VMware ESXi 5.5 Update 3 hosts to fail with the error: Unexpected signal: 1 will see an log message similar to the following in the viiiWare .log file: [YYYY-MM-DD]