COS Panic: Int3 @ mp_register_ioapic

Коллеги, у кого ESX4 работает со сторонними агентами, перед обновлением до Update 1 ознакомьтесь со статьей в безе знаний http://kb.vmware.com/kb/1016070

Upgrading ESX 4.0 to 4.0 U1 using Update Manager fails or times out and rebooting the host results in a purple diagnostic screen

Symptoms

When attempting to upgrade ESX 4.0 to ESX 4.0 Update 1, you may experience the following symptoms:

• Update Manager (VUM) upgrade operation fails or times out at 33%.
• Upon reboot, the host that was being upgraded displays a purple diagnostic screen with the following error:
  
  COS Panic: Int3 @ mp_register_ioapic

Resolution

Who is affected

Customers using VMware vSphere 4 upgrading to Update 1 with 3^rd party management agents running.

Solution

To avoid this issue, prior to the update, disable all 3rd party management agents running on the ESX 4.0.0 server before applying the update.

Note: The 3rd party management agents can be enabled after the upgrade is completed.

If you have already updated the ESX host, do not reboot the ESX host. Open a support request with VMware support. For more information, see How to Submit a Support Request.

WARNING: Rebooting the host means the host has 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 in recovering those virtual machines.