VMware has republished the patch for ESXi 5.5 (ESXi550-201504002) that has been recalled this week.

Product: VMware ESXi 5.5

Release date: May 8, 2015

Patch: ESXi550-201505002

Build: 2718055

Build (security only): 2702869

Links: KB2114245 | Download

The update resolves 41 issues including the following:

Virtual machines with Linux guest operating system might stop responding due to kernel panic in balloon driver. You might see backtrace similar to the following:

[ ] :vmmemctl:Balloon_QueryAndExecute+0x67/0x9cc

[ ] :vmmemctl:OS_UnmapPage+0x102/0x2a0

[ ] autoremove_wake_function+0x0/0x2e

[ ] autoremove_wake_function+0x0/0x2e

[ ] :vmmemctl:OS_UnmapPage+0x8/0x2a0

[ ] kthread+0xfe/0x132

[ ] child_rip+0xa/0x11

[ ] keventd_create_kthread+0x0/0xc4

[ ] kthread+0x0/0x132

[ ] child_rip+0x0/0x11

The vFlash cache metric counters such as FlashCacheIOPs, FlashCacheLatency, and FlashCacheThroughput might not be available when CBT is enabled on a virtual disk. Error messages similar to the following are logged in the stats.log file:

nnnn-nn-nnT06:17:20.200Z [nnnnnnnn error 'Statssvc.vim.PerformanceManager'] CollectVmVdiskStats : Failed to get VFlash Cache stats for vscsi id scsi0:0 for vm 3

nnnn-nn-nnT06:17:40.189Z [nnnnnnnn error 'Statssvc.vim.PerformanceManager'] GetVirtualDiskVFCStats: Failed to get VFlash Cache stat values for vmdk scsi0:0. Exception VFlash Cache filename not found!

…

…

nnnn-nn-nnT06:18:20.181Z [nnnnnnnn error 'Statssvc.vim.PerformanceManager'] GetVirtualDiskVFCStats: Failed to get VFlash Cache stat values for vmdk scsi0:0. Exception VFlash Cache filename not found!

When you delete a VDI environment enabled desktop pool, the VMDK files of the other virtual machine from a different desktop pool might get deleted. Multiple virtual machines from different desktop pools might get affected. This happens after you delete the disk, and the parent directory gets deleted due to an error. The directory is perceived as empty, even though it is not. An error message similar to the following might be displayed:

nnnn-nn-nnT14:08:03.408-07:00 [nnnnn info 'Default' opID=nnnnnnnn] [VpxLRO] -- ERROR task-19533 -- vm-1382 -- vim.ManagedEntity.destroy: vim.fault.FileNotFound:

--> Result:

--> (vim.fault.FileNotFound) {

--> dynamicType = >unset>,

--> faultCause = (vmodl.MethodFault) null,

--> file = "[cntr-1] guest1-vm-4-vdm-user-disk-D-nnnnnnnn-nnnn-nnnn-nnnn- nnnnnnnnnnnn.vmdk",

--> msg = "File [cntr-1] guest1-vm-4-vdm-user-disk-D-nnnnnnnn-nnnn-nnnn-nnnn- nnnnnnnnnnnn.vmdk was not found",

--> }

--> Args

The IBM BladeCenter HS23 server that boots from a USB device is unable to write the coredump file when the active coredump partition is configured on an USB device. A purple screen displays the dump attempting to initiate but does not complete.

Attempts to upgrade ESXi from 5.1 to 5.5 when using the Mellanox Connect X3 driver might fail due to the way in which the VMNICs are enumerated.

An ESXi host might show as disconnected in vCenter Server when the hostd process is not responding. This issue might occur when there is a Permanent Device Loss (PDL) and the underlying file system fails to notify pending All Paths Down (APD) events to the Pluggable Storage Architecture (PSA) layer.

To debug performance issues related to NFS datastores, DAVG has been added to the esxtop utility.

If you want to get notified when new patches are released, subscribe to virten.net via Email in the sidebar.

The latest ESXi 5.5.0 Build number is now: 2718055

Updated: ESXi Release and Build Number History

Updated: VMware Product Latest Version

Updated: ESXi Image Profiles