VMware ESX 4 – COS Panic: Int3 @ mp_register_ioapic

 Allgemein, Knowledge Base, VMware, VMware Update Manager  Kommentare deaktiviert für VMware ESX 4 – COS Panic: Int3 @ mp_register_ioapic
Dez 092009
 

Via VMware KB

VMware KB: Due to a possible dead lock on rpmdb, upgrading ESX 4.0 to 4.0 Update 1 can fail or time out and leave the host in an unusable state

Due to a possible dead lock on rpmdb, upgrading ESX 4.0 to 4.0 Update 1 can fail or time out and leave the host in an unusable state

Symptoms
When attempting to upgrade ESX 4.0 to ESX 4.0 Update 1 (U1), you may experience these symptoms:

* Upgrade operation may fail or hang and can result in an incomplete installation
* Upon reboot, the host that was being upgraded may be left in an inconsistent state and may display a purple diagnostic screen with the following error:

COS Panic: Int3 @ mp_register_ioapic

Purpose
ESX 4.0 U1 includes an upgrade to glibc version 5.3 which implements a change in locking mechanism compared to glibc version 5.2 already installed with ESX 4.0. If rpm command is run during the installation of ESX 4.0 U1, a dead lock may be placed on rpmdb. For more information, see RedHat PR 463921.

As a result, upgrading ESX 4.0 to 4.0 U1 can fail or time out and leave the host in an unusable state.
While this issue is not hardware vendor specific, this has been reported to occur on HP Proliant systems if Insight Management Agents are already installed and running on the host being upgraded. Investigations into this issue revealed that Insight Management Agents run rpm commands on a regular basis which triggers the deadlock during the U1 installation. This can also occur on any system from other vendors that has a process or an application running rpm, or if you happen to manually run the rpm command, like rpm -qa, while Update 1 installation is in progress.

Note: VMware esxupdate tool can be used standalone and is also used by VMware Update Manager and VMware Host Update Utility.

Resolution
Who is affected

1. Customers using VMware vSphere 4 upgrading to ESX 4.0 U1 on HP Proliant systems with a supported version of HP Insight Management Agents running.
2. Customers running rpm commands on systems from any vendor while upgrading to ESX 4.0 U1.

This affects any of the following upgrading scenarios:

* Upgrade using Update Manager
* Upgrade using esxupdate
* Upgrade using vSphere Host Update Utility

Note: ESXi is not affected.

Note: If you want to install the update, you must download the update manually. The update is no longer available for automatic download in Update Manager and the vSphere Update Utility. You can find the update on the VMware Downloads site and copy the download to your local depot as needed.
Solution
To avoid this issue:

1. Do not run rpm commands on any host while the Update 1 installation is in progress
2. If Update 1 is being installed on a HP Proliant Server, disable HP Insight Management Agents running on the ESX 4.0.0 host prior to installing Update 1.

HP Insight Management Agents can be stopped using the following sequence of commands:

* service hpsmhd stop
* service hp-snmp-agents stop
* service hp-health stop

HP management agents automatically restart after the upgrade completes and the system is rebooted.

If you meet one or both of the conditions of Who is Affected and you already ran the Update 1 installation but have not rebooted the host, do not reboot the ESX host. Contact VMware Technical Support for assistance. For more information, see How to Submit a Support Request.

WARNING: Rebooting the host means the host may need to be reinstalled because it is not recoverable after a reboot.

WARNING: If you have virtual machines running on local storage, they may not be retained if you reinstall ESX 4.0 as a result of this issue. Contact VMware Support for assistance before reinstalling.

Technorati-Tags: , , , , ,

 Posted by at 09:48

Enabling the VMware vCenter Update Manager plugin in 4.x generates an error

 Allgemein, Knowledge Base, Updates, vCenter Server, VMware, VMware Update Manager  Kommentare deaktiviert für Enabling the VMware vCenter Update Manager plugin in 4.x generates an error
Sep 042009
 

Source: http://kb.vmware.com/

Symptoms

You may experience these symptoms:
Attempting to enable the VMware vCenter Update Manager plugin fails
You receive the following error:

There was an error connecting to vmware vcenter update manager – IPADDRESSOFVC:8084
Vmacore::Exception: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

or

The request failed because of a connection failure.

Resolution

Enabling the VMware vCenter can fail if you are using a remote SQL database with Windows authentication and the Update Manager service is set to log on as the local system account.
Change the service to login as the same Windows NT account that has been given dbo permissions to the SQL database.

Make sure the vci-integrity.xml file, located at C:\Program Files\VMware\Infrastructure\Update Manager, has the correct vCenter IP address. If the IP address is incorrect, update it and restart the Update Manager service.

Setting up VMware Update Manager Download Service for Isolated Networks

 Updates, VMware, VMware ESX, VMware Update Manager, VMware Virtual Infrastructure  Kommentare deaktiviert für Setting up VMware Update Manager Download Service for Isolated Networks
Jan 212009
 

VMware Communities: Setting up Vmware Update Manager Download Service for Isolated Networks

Patching Offline ESX servers with Vmware Update Manager

This is my brief guide to what I did to setup patching for isolated networks, like those in intellegence communities, etc. This is meant to help fill in some of the gaps that the documentation left in the process.

Install Update Manager Download Service

Setup a machine to be your Update Manager Download system:

* This machine must have Internet access.
* This system will require another database beyond what the Update Manager in Virtual Center uses, so you may not want to install it there.
* Also, you will need to burn CDs/DVDs or transfer files to a device
* This all being said, a workstation is a good candidate system

Install the Update Manager Download Service on the above machine. Take note of the installation folder and the folder where the downloads will be stored.

* Files are located in „umds“ folder of the Virtual Center installation CD image
* Open the VMware-UMDS.exe file to install
* Select to use the local SQL 2005 Express database server

Download Current Updates

The best thing to do is setup a Windows Scheduled Task that downloads the updates automatically. The first step is to create a script to accomplish this manually then you can make it a scheduled task.

To get current downloads:

* Change to the „C:\Program Files\VMware\Infrastructure\Update Manager“ directory
* Run the program: vmware-umds –download (or „vmware-umds -D“)
* Get coffee! Really, the first run takes a loonngg time.

NOTE: It is possible to configure the download to only retrieve ESX host updates, Windows VM updates and/or Linux VM updates. To change which updates are downloaded use the following syntax:

* vmware-umds -S -h true | false
* vmware-umds -S -w true | false
* vmware-umds -S -l true | false

For example: vmware-umds -S -h true will d/l ESX host patches, vmware-umds -S -w false will NOT d/l Windows VM patches, etc. This can be useful if you want to verify the process but not spend time waiting for the Windows patches to download. Before running „vmware-umds -D“, disable Windows and Linux and verify that the ESX patches are downloaded successfully

Once downloads are done you need to export to a local file repository:

* Change to the „C:\Program Files\VMware\Infrastructure\Update Manager“ directory
* Run the program: vmware-umds -E –dest -s 2007-01-01T00:00:00 -t 2007-12-31T23:59:59
* This downloads all the patches for 2007, specify different time ranges as required.

Once exported you need to export your repository to some sort of portable media, say a DVD (most likely a DL from what I have already seen!!!)

Import Updates to Virtual Center on Isolated Network

Now that your Internet connect machine has done all the dirty work, you need to get the updates into Virtual Center’s Update Database:

* Get you update media connected to Virtual Center so it can access the files
* Change to the „C:\Program Files\VMware\Infrastructure\Update Manager“ directory on Virtual Center
* Run the program: vmware-updateDownloadCli.exe –update-path –config-import windows esx –vc-user

This is a very brief explanation of what to do. See these fine documents below for more stuff:

, , ,

 Posted by at 12:43