Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

Search the VMware Knowledge Base (KB)

View by Article ID

VMware ESXi 4.0, Patch ESXi400-201005402-BG: Updates VMware Tools

Details

Release Date: May 27, 2010

Download Size:
180.9MB
Download Filename:
ESXi400-201005001.zip
md5sum:
f2295659befeb4da2542811d3c3d5467
sha1sum:
a0e5a9211f0faf5caadbd3c3a1fd7b421eb0f473

Product Versions	ESXi 4.0
Build	256968 Also see KB 1012514.
Patch Classification	Critical
Host Reboot Required	No
Virtual Machine Migration or Shutdown Required	No
PRs Fixed	505463
Affected Hardware	N/A
Affected Software	N/A
Related CVE numbers	N/A

Solution

Summaries and Symptoms

The VMware Snapshot Provider service is not listed in the Services panel. The quiesced snapshots do not use VMware Tools VSS components in Windows Server 2008 R2 or Windows 7 operating systems. This issue is seen when the user or backup software performs a quiesced snapshot on virtual machines on ESXi 4.0 hosts. This patch fixes the issue.

Deployment Considerations

Install the firmware patch bulletin ESXi400-201005401-SG for a complete fix.

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 http://support.vmware.com/selfsupport/download/ and installing the bulletin by using the vihostupdate command through the vSphere CLI. For details, see the vSphere CLI Installation and Reference 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

1 2 3 4 5

1 2 3 4 5

Actions

Bookmark Document

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)