Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Virtual machines may unexpectedly reboot when using VMware HA with virtual machine monitoring on ESX 3.5 Update 3 (1007899)

Last Updated: 3/20/2024Categories: Total Views: 46135Language:
Chinese (Simplified)Portuguese (European)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Virtual machines may unexpectedly reboot after a VMotion migration to an ESX 3.5 Update 3 (build 123630) host.

Virtual machines may unexpectedly reboot after a Power On operation on an ESX 3.5 Update 3 (build 123630) host, when the VMware High Availability (HA) feature with virtual machine monitoring is active.

This issue may following the periodic vpxuser password update and service restart, as shown in the logs:

[2009-06-03 11:18:55.759 'TaskManager' 110087088 info] Task Created : haTask-ha-folder-root-vim.host.LocalAccountManager.updateUser-1870238977
[2009-06-03 11:19:18.132 'App' 3076440992 info] END SERVICES ....
[2009-06-03 11:20:45.968 'App' 65657776 verbose] [vpxaVmFailover::NotifyVmFailover] VM 2, time 1244042445, failure type 0, interval 40, uptime 4410909
[2009-06-03 11:20:45.968 'App' 65657776 verbose] [vpxaVmFailover::NotifyVmFailover] VM 6, time 1244042445, failure type 0, interval 40, uptime 6678154
[2009-06-03 11:20:45.968 'App' 65657776 verbose] [vpxaVmFailover::NotifyVmFailover] VM 7, time 1244042445, failure type 0, interval 40, uptime 5941025
[2009-06-03 11:20:45.968 'App' 65657776 verbose] [vpxaVmFailover::NotifyVmFailover] VM 8, time 1244042445, failure type 0, interval 40, uptime 66781 54
[2009-06-03 11:20:45.968 'App' 65657776 verbose] [vpxaVmFailover::NotifyVmFailover] VM 9, time 1244042445, failure type 0, interval 40, uptime 4737749

/var/log/vmware/hostd.log shows:

[2009-03-20 04:44:35.252 'TaskManager' 3076453280 info] Task Created : haTask-512-vim.VirtualMachine.reset-47992
[2009-03-20 04:44:35.323 'ha-eventmgr' 3076453280 info] Event 8420 : Win2003-1 on esx1.xyz.com in ha-datacenter is reset
[2009-03-20 04:44:35.323 'vm:/vmfs/volumes/48331160-05c64c5c-edf0-001e0bd8c708/Win2003-1/Win2003-1.vmx' 3076453280 info] State Transition (VM_STATE_ON -> VM_STATE_RESETTING)

Resolution

A virtual machine may reboot itself if:

The virtual machine is running on a ESX 3.5 Update 3 host, either by virtue of VMotion or a Power On operation

AND

The host has VMware HA enabled with the virtual machine monitoring option active.

Virtual machine monitoring is dependent on VMware tools heartbeats to determine the state of the virtual machines.

With ESX Server 3.5 Update 3 after a VMotion or a Power On operation, the host agent running on the ESX server may delay sending the heartbeat state of the virtual machine to the Host. VMware HA detects this as a failure of the virtual machine and attempts to restart the virtual machine.

The issue has been resolved in VirtualCenter 2.5 Update 4. You can download VirtualCenter 2.5 Update 4 from the Download Center.

If you cannot upgrade, perform one of the following workarounds.

Workaround 1: Disabling virtual machine monitoring

To disable virtual machine monitoring:

Right-click the VMware HA cluster and choose Edit Settings.

Note: This feature can also be enabled for a new cluster on the VMware HA page of the New Cluster wizard.

In the Cluster Settings dialog box, select VMware HA in the left column.

Deselect Enable virtual machine monitoring.

Click OK.

Workaround 2: Setting hostd heartbeat delay to 0

Notes:

If you perform workaround 2, the heartbeat alarm in VirtualCenter (for virtual machines running on the ESX 3.5 Update 3 host) may go red until the VMware Tools inside GOS starts to heartbeat.

Before you begin please refer to Restarting the Management agents on an ESX Server (1003490) for important information on restarting the mgmt-vmware service.

To set the hostd heartbeat delay to 0:

Disconnect the host from VirtualCenter. Right-click on the host in VMware Infrastructure (VI) Client and choose Disconnect.

Log in as root to the ESX host with an SSH client.

Open the file /etc/vmware/hostd/config.xml in a text editor.

Set the heartbeatDelayInSecs tag under vmsvc to 0 seconds:

<vmsvc>
<heartbeatDelayInSecs>0</heartbeatDelayInSecs>
<enabled>true</enabled>
</vmsvc>

Save your changes and exit.

Restart the management agents for this change to take effect. For more information, see Restarting the Management agents on an ESX Server (1003490).

Reconnect the host in VirtualCenter. Right-click on the host in VI Client and choose Connect.

Notes:

Setting heartbeatDelayInSecs to 0 does not disable virtual machine monitoring.

When any ESX patches are applied, changes to the config.xml file are over-written.

Related Information

如果在 ESX 3.5 Update 3 上使用具有虚拟机监控的 VMware HA，虚拟机可能会意外重新引导
ESX 3.5 Update 3 で、仮想マシンの監視が有効になっている VMware HA を使用している場合に仮想マシンが突然再起動することがある
Máquinas virtuais podem reinicializar inesperadamente durante o uso do VMware HA com monitoramento de máquina virtual no ESX 3.5 Update 3

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware VirtualCenter

VMware ESX Server

Related Versions:

VMware VirtualCenter 2.5.x

VMware ESX Server 3.5.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant