Summary
This patch resolves an issue with systems installed with patch bundle ESX350-200806201-UG where virtual machines fail to power on or VMotion successfully.
This patch is specifically targeted for customers who have installed or fully upgraded to ESX 3.5 Update 2, or who have applied the ESX350-200806201-UG patch to ESX 3.5 or ESX 3.5 Update 1 hosts.
To determine if ESX350-200806201-UG is already installed on your system:
-
From the service console, run esxupdate -l query and examine the output. If ESX350-200806201-UG is not listed in the output, this patch is not applicable.
The output from the following example shows a system that requires the patch.
# esxupdate -l query | grep 6201
ESX350-200806201-UG 06:34:57 08/14/08 Updates VMkernel, Service Console, hostd
-
From Update Manager, create a baseline with both patches and then attach it to the ESX hosts. Run a scan. If the host (or hosts) is compliant with the baseline, this patch is not applicable.
Symptoms
You are unable to power on virtual machines. VI Client displays the error:
A General System error occurred: Internal error.
The following message is logged in the vmware.log file for the virtual machine:
This product has expired. Be sure that your host machine's date and time are set correctly.
There is a more recent version available at the VMware web site: http://www.vmware.com/info?id=4.
--------------
Module License Power on failed.
Deployment Considerations
If you have a cluster with DRS enabled, you must put the cluster in manual mode.
VMotion migration of virtual machines can be used if the destination host is not affected by this issue or has been updated with the express patch.
Patch Download and Installation
Patches are typically installed using VMware Update Manager. For details on using this tool, see the Administration Guide.
To download and install this patch manually using esxupdate from the command-line:
-
-
Under Express Patches, step 2, click the link VMware ESX 3.5 Update 2 Patch and save the file when prompted.
-
Put the patch on the ESX host. Use an SSH/SCP utility or other relevant tool. For example:
cd /var/updates
# esxcfg-firewall -e sshClient
# scp user@bastion-host:/tmp/ESX350-200806812-BG.zip
user@bastion-host's password:
ESX350-200806812-BG.zip 100% 104MB 10.0MB/s 00:10
Here, the user:
-
Changes directories into /var/updates (your file location can be different).
-
Enables SSH (it is disabled by default).
-
Uses SCP to copy the file from the DMZ host (named bastion-host), onto which he previously downloaded the file under the /tmp directory.
-
Verify the file size and md5sum. For example:
# ls -logh
total 106720
-rw-r--r-- 1 104M Aug 14 07:45 ESX350-200806812-BG.zip
# md5sum ESX350-200806812-BG.zip
0011986033c66ad582da899acba32dfb ESX350-200806812-BG.zip
-
Unzip the file and change to the unzipped directory.
# unzip ESX350-200806812-BG.zip
# cd ESX350-200806812-BG
-
(Optional) Double-check the patch information.
# esxupdate info
The Summary for the patch says, "Fix the time bomb issue for U2." Other useful information about the patch is listed also, including required and obsoleted patches.
-
Apply the patch.
# esxupdate update
INFO: No repository URL specified, going with file:///var/updates/ESX350-200806812-BG
INFO: Configuring...
INFO: Preparing to install ['ESX350-200806812-BG']...
DOWNLOADING: <RPMs included in this patch are listed> ...
<more INFO lines>
INFO: Transaction(s) Complete
INFO: Shutting down hostd...
INFO: Running esxcfg-boot to regenerate initrds...
INFO: Restarting hostd...
INFO: --- TOTALS: 2 packages installed, 0 pending or failed, 0 excluded ---
INFO: Install of ['ESX350-20080612-BG'] succeeded.
-
In VI Client, power on a virtual machine. It should now start with no error message displayed.
Related documents:
| 
