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

VMware ESXi 4.1, Patch Release ESXi410-201301401-SG (2041338)

  • 0 Ratings

Details

Product Version
ESXi 4.1
Patch Classification
Security
See KB 2014447 if using Update Manager 5.0
Build Information
For build information, see KB 2041332.
Host Reboot Required
Yes
Virtual Machine Migration or Shutdown Required
Yes
PRs Fixed
655241, 928757, 931609, 941434, 949845, 979336, 961935, 932422
Affected Hardware
N/A
Affected Software
N/A
Related CVE numbers
CVE-2011-3102, CVE-2012-2807, CVE-2013-1405

Solution

Summaries and Symptoms

This patch resolves the following issues:

  • Attempts to PXE boot virtual machines that use the VMXNET3 network adapter, by using Microsoft Windows Deployment Services (WDS) might fail with 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 you Windows installation disc and restart your computer.
    2. Choose your language setting, and then click "Next".
    3. Click "Repair your computer".
    If you do not have the disc, contact your system administrator or computer manufacturer for assistance.
    Status: 0xc0000001
    Info: The boot selection failed because a required device is inaccessible.


  • Virtual machines might stop responding during a snapshot removal due to a forced synchronous consolidation between the snapshot disk and the parent disk. This occurs when the virtual machine is running a heavy I/O workload during snapshot consolidation.
    To disable synchronous consolidation add the configuration option snapshot.asyncConsolidate.forceSync = "FALSE" to the VMX file.

  • The ESXi host stops responding with a purple screen, when a pseudo lun of class SCSI_CLASS_RAID(0xc) with same naa.id as used by a pRDM in a virtual machine is presented as the new lun and a rescan is performed.


  • If an independent disk is deleted from a virtual machine, attempts to create a quiesced snapshot of a virtual machine might fail because the disk mode data for a given SCSI node might not be current.
    Error message similar to the following might be displayed:
    Status: An error occurred while quiescing the virtual machine.
    See the virtual machine's event log for details.
    The log files might contain entries similar to the following:
    ToolsBackup: changing quiesce state: STARTED -> DONESnapshotVMXTakeSnapshotComplete done with snapshot 'back': 0SnapshotVMXTakeSnapshotComplete: Snapshot 0 failed: Failed to quiesce the virtual machine. (40).

  • A virtual machine might lose network connectivity from external environment after vMotion with vNetwork Distributed Switch environment. You might encounter this issue when all of the following configuration scenarios are true:
    • The virtual machine network portgroup is configured on vNetwork Distributed Switch.
    • The virtual machine is configured with vmxnet2 (enhanced) or Flexible(vmxnet) NIC.
    • The configuration with virtual machine network portgroup security setting is set to Reject "MAC Address Change".


  • There is a notification that the current version of VMware Tools is out of date and prompts you to perform an automatic upgrade, if required.

This patch resolves the following security issues:

  • The ESX/ESXi userworld libxml2 library is updated to resolve multiple security issues. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CVE-2011-3102 and CVE-2012-2807 to these issues.

  • ESXi contains a vulnerability in the handling of the management authentication protocol. To exploit this vulnerability, an attacker must convince ESXi to interact with a malicious server as a client. Exploitation of the issue may lead to code execution on the client system. To reduce the likelihood of exploitation, ESXi should be deployed on an isolated management network.
    The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2013-1405 to this issue.

 


Deployment Considerations

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

Patch Download and Installation

The typical way to apply patches to ESXi hosts is through the VMware Update Manager. For details, see the VMware vCenter Update Manager Administration Guide.

ESXi hosts can also be updated using vSphere Host Update Utility or by manually downloading the patch ZIP file from the VMware download page and installing the bulletin by using the vihostupdate command through the vSphere CLI. For details, see the vSphere Command-Line Interface Installation and Scripting Guide and the vSphere Upgrade Guide.

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.

Feedback

  • 0 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.
  • 0 Ratings
Actions
KB: