Search the VMware Knowledge Base (KB)
View by Article ID

VMware ESXi 5.1, Patch ESXi510-201212401-BG: Updates esx-base (2035777)

  • 5 Ratings


Release date: December 20, 2012

Patch Category Bug Fix
Patch Severity Important
Build For build information, see KB 2035775.
Host Reboot Required Yes
Virtual Machine Migration or Shutdown Required Yes
Affected Hardware N/A
Affected Software N/A
VIBs Included VMware:esx-base:5.1.0-0.9.914609
PRs Fixed 916421, 924167, 926287, 932615, 936916, 939933
Related CVE numbers N/A


This patch updates the esx-base VIB to resolve the following issues:

  • PR916421: The vCenter Server Agent (vpxa) stops responding when hostd fails to populate the correct VLAN range information of Fibre Channel over Ethernet (FCoE) adapters if the configured VLAN IDs fall under the range of 32n - 1 (for example 31, 63, 127, and so on).

  • PR924167: An ESXi host stops responding and displays a purple diagnostic screen when you attempt to power on a virtual machine that uses a pass-through PCI device. For more information, see KB 2039030.

  • PR926287: ESXi 5.1 does not provide advanced parameters QFullSampleSize and QFullThreshold which are required to enable adaptive queue depth algorithm. This patch resolves the issue by providing the advanced parameters to set the values globally.

    Note: You can also use the esxcli command to set these values per device. If both the options (esxcli and advanced parameters) are used, the per device values take precedence.

  • PR932615: An ESXi 5.1 host stops responding when running a virtual machine and might display a purple diagnostic screen with messages similar to the following:

    cpu4:8243)@BlueScreen: NOT_IMPLEMENTED bora/vmkernel/sched/memsched.c:17724
    cpu4:8243)Code start: 0x41802b200000 VMK uptime: 10:19:25:27.335
    cpu4:8243)0x412200cdbaf0:[0x41802b27abff]PanicvPanicInt@vmkernel#nover+0x56 stack: 0x3000000008
    cpu4:8243)0x412200cdbbd0:[0x41802b27b4a7]Panic@vmkernel#nover+0xae stack: 0x100000000000000
    cpu4:8243)0x412200cdbc50:[0x41802b3d88eb]MemSched_WorldCleanup@vmkernel#nover+0x426 stack: 0x4100018a4fb0
    cpu4:8243)0x412200cdbef0:[0x41802b3033b8]WorldCleanup@vmkernel#nover+0x1cb stack: 0x4700cdbf40
    cpu4:8243)0x412200cdbf60:[0x41802b303829]WorldReap@vmkernel#nover+0x318 stack: 0x0
    cpu4:8243)0x412200cdbff0:[0x41802b2483c8]helpFunc@vmkernel#nover+0x517 stack: 0x0
    cpu4:8243)0x412200cdbff8:[0x0] stack: 0x0
    cpu4:8243)base fs=0x0 gs=0x418041000000 Kgs=0x0


    2012-10-10T16:31:17.308Z cpu3:11896)@BlueScreen: #PF Exception 14 in world 11896:vmast.11895 IP 0x418035c80a1e addr 0x410401501820
    2012-10-10T16:31:17.308Z cpu3:11896)Code start: 0x418035c00000 VMK uptime: 28:18:32:16.787
    2012-10-10T16:31:17.310Z cpu3:11896)0x412239e1bcd0:[0x418035c80a1e]PShareHashTableWalk@vmkernel#nover+0x219 stack: 0x412239e1bd24
    2012-10-10T16:31:17.311Z cpu3:11896)0x412239e1bd50:[0x418035c81c6d]PShare_RemoveHint@vmkernel#nover+0x178 stack: 0x412239e1bda0
    2012-10-10T16:31:17.313Z cpu3:11896)0x412239e1bdd0:[0x418035cca39c]VmMemCow_PShareRemoveHint@vmkernel#nover+0x123 stack: 0xcd499
    2012-10-10T16:31:17.314Z cpu3:11896)0x412239e1be30:[0x418035ccd70a]VmMemCowPFrameRemoveHint@vmkernel#nover+0x6d stack: 0x410000000000
    2012-10-10T16:31:17.316Z cpu3:11896)0x412239e1bfa0:[0x418035ccef79]VmMemCowPShareFn@vmkernel#nover+0x548 stack: 0x412239e1bff0
    2012-10-10T16:31:17.317Z cpu3:11896)0x412239e1bff0:[0x418035cb13c4]VmAssistantProcessTask@vmkernel#nover+0x19f stack: 0x0
    2012-10-10T16:31:17.318Z cpu3:11896)0x412239e1bff8:[0x0] stack: 0x0
    2012-10-10T16:31:17.330Z cpu3:11896)base fs=0x0 gs=0x418040c00000 Kgs=0x0

  • PR936916: When a host with SMBIOS 2.6 or higher is upgraded to ESXi 5.1 or if the BIOS on an ESXi 5.1 host is upgraded to SMBIOS 2.6 or higher, the following Virtual Machine Message is displayed when you power a virtual machine on:

    This virtual machine might have been moved or copied. In order to configure certain management and networking features, VMWare ESX needs to know if this virtual machine was moved or copied. If you don't know, answer "I...

    • Cancel
    • I moved it
    • I copied it

  • PR939933: Attempts to migrate virtual machines by performing a vMotion operation from ESX/ESXi 4.1 or ESXi 5.0 to ESXi 5.1 might fail with the following error if checkpoint.cptConfigName value is set in the VMX configuration file of the virtual machine:

    Failed to resume destination VM: Not found.
    vMotion migration [xxxxx:xxxxxxxxx] could not find destination swapfile. Verify matching source and destination host swap settings, including matching VM or swapfile path UUIDs, and storage accessibility.

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.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 5 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 5 Ratings