Portal Home > Knowledgebase > VMware Knowledge Base > VMware ESX 4.0, Patch ESX400-201002401-BG: Updates vmkernel64, vmx, hostd, etc

VMware ESX 4.0, Patch ESX400-201002401-BG: Updates vmkernel64, vmx, hostd, etc


Release Date: March 3, 2010
Download Size:
607.4 MB
Download Filename:

Product VersionsESX 4.0
Also see KB 1012514.
Patch ClassificationCritical
Host Reboot RequiredYes
Virtual Machine Migration or Shutdown RequiredYes
PRs Fixed515565, 479281, 494724,
487032, 485851, 473772,
490319, 501772, 499703
Affected HardwareN/A
Affected SoftwareN/A
Modified VIBs Includedvmware-esx-apps
Related CVE numbersN/A


Summaries and Symptoms

This patch provides support and fixes the following issues:

  • On some systems under heavy networking and processor load (large number of virtual machines), some NIC drivers might randomly attempt to reset the device and fail.
    The VMkernel logs generate the following messages every second:
    Oct 13 05:19:19 vmkernel: 0:09:22:33.216 cpu2:4390)WARNING: LinNet: netdev_watchdog: NETDEV WATCHDOG: vmnic1: transmit timed out
    Oct 13 05:19:20 vmkernel: 0:09:22:34.218 cpu8:4395)WARNING: LinNet: netdev_watchdog: NETDEV WATCHDOG: vmnic1: transmit timed out
  • ESX hosts do not display the proper status of the NFS datastore after recovering from a connectivity loss.
    Symptom: In vCenter Server, the NFS datastore is displayed as inactive.
  • When using NPIV, if the LUN on the physical HBA path is not same as the LUN on the virtual port (VPORT) path, though the LUNID:TARGETID pairs are same, then I/O might be directed to the wrong LUN causing a possible data corruption. For more information, see Possible data corruption due to error during NPIV VPORT discovery process (1015290).
    Symptom: If NPIV is not configured properly, I/O might be directed to the wrong disk.
  • On Fujitsu systems, the OEM-IPMI-Command-Handler that lists the available OEM IPMI commands do not work as intended. No custom OEM IPMI commands are listed, though they were initialized correctly by the OEM. After applying this fix, running the VMware_IPMIOEMExtensionService and VMware_IPMIOEMExtensionServiceImpl objects displays the supported commands as listed in the command files.
  • Provides prebuilt kernel module drivers for Ubuntu 9.10 guest operating systems.
  • Adds support for upstreamed kernel PVSCSI and vmxnet3 modules.
  • Provides a change to the maintenance mode requirement during Cisco Nexus 1000V software upgrade. After installing this patch if you perform Cisco Nexus 1000V software upgrade, the ESX host goes into maintenance mode during the VEM upgrade.
  • In certain race conditions, freeing journal blocks from VMFS filesystems might fail. The WARNING: J3: 1625: Error freeing journal block (returned 0) for 497dd872-042e6e6b-942e-00215a4f87bb: Lock was not free error is written to the VMware logs.
  • Changing the resolution of the guest operating system over a PCoIP connection (desktops managed by View 4.0) might cause the virtual machine to stop responding.

    Symptoms: The following symptoms might be visible:
    • When you try to connect to the virtual machine through a vCenter Server console, a black screen appears with theUnable to connect to MKS: vmx connection handshake failed for vmfs {VM Path} message.
    • Performance graphs for CPU and memory usage in vCenter Server drop to 0.
    • Virtual machines cannot be powered off or restarted.
    • In VMware View managed desktops, you may see the error:

      The assigned desktop source for the desktop is not currently available. Please try connecting to the desktop again later, or contact your systems administrator.

Deployment Considerations

None beyond the required patch bundles and reboot information listed in the table above.

Based on VMware KB 1017458

Also Read