Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

My Subscriptions

Loading

Knowledge Base

PSOD hosts seem to PSOD when a particular VM is migrated to them (52241)

Last Updated: 1/4/2018Categories: TroubleshootingTotal Views: 22Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

hostname: vdc-esxalc02s08.vdc.adm

VMware ESXi 5.5.0 build-2403361 and this is 5.5 Update 2

server model and BIOS version
HP ProLiant DL580 G7 | BIOS: P65 | Date: 10/01/2013

PSOD Stacktrace
================================
2017-11-13T11:03:22.328Z cpu72:43960)WARNING: Heartbeat: 785: PCPU 13 didn't have a heartbeat for 21 seconds; *may* be locked up.
2017-11-13T11:03:22.328Z cpu67:43966)WARNING: Heartbeat: 785: PCPU 8 didn't have a heartbeat for 21 seconds; *may* be locked up.

2017-11-13T11:03:15.328Z cpu5:283862)ALERT: NMI: 709: NMI IPI received. Was eip(base):ebp:cs [0x76b18(0x418035e00000):0x41255359dc18:0x4010](Src 0x1, CPU5)

2017-11-13T11:03:22.396Z cpu67:43966)Panic: 721: Panic from another CPU (cpu 67, world 43966): ip=0x41803617819d randomOff=0x35e00000:
PCPU 8: no heartbeat (2/2 IPIs received)
2017-11-13T11:03:22.396Z cpu67:43966)Panic: 903: Saved backtrace: pcpu 8 Heartbeat NMI
2017-11-13T11:03:22.396Z cpu67:43966)pcpu 8 Heartbeat NMI: 0x4125c985dc18:[0x418035e76b18]MCSWaitForUnblock@vmkernel#nover+0x108 stack:
2017-11-13T11:03:22.396Z cpu67:43966)pcpu 8 Heartbeat NMI: 0x4125c985ddf8:[0x418035e7781c]MCSLockRWContended@vmkernel#nover+0x434 stack:

2017-11-13T11:03:22.460Z cpu72:43960)VMware ESXi 5.5.0 [Releasebuild-2403361 x86_64]
PCPU 13: no heartbeat (2/2 IPIs received)

2017-11-13T11:03:22.462Z cpu72:43960)@BlueScreen: PCPU 13: no heartbeat (2/2 IPIs received)
2017-11-13T11:03:22.462Z cpu72:43960)Code start: 0x418035e00000 VMK uptime: 57:19:03:05.381
2017-11-13T11:03:22.462Z cpu72:43960)Saved backtrace from: pcpu 13 Heartbeat NMI
2017-11-13T11:03:22.463Z cpu72:43960)0x4125c1f1dc18:[0x418035e76b1b]MCSWaitForUnblock@vmkernel#nover+0x10b stack: 0x4125c9861000402f
2017-11-13T11:03:22.463Z cpu72:43960)0x4125c1f1ddf8:[0x418035e7781c]MCSLockRWContended@vmkernel#nover+0x434 stack: 0x410a5a66b508
2017-11-13T11:03:22.464Z cpu72:43960)0x4125c1f1de38:[0x418035e77c94]MCS_DoAcqReadLockWithRA@vmkernel#nover+0x12c stack: 0x4125c1f1de78
2017-11-13T11:03:22.464Z cpu72:43960)0x4125c1f1de68:[0x418035e90835]RefCount_ReaderWait@vmkernel#nover+0xc9 stack: 0x4125c1f1dec8
2017-11-13T11:03:22.465Z cpu72:43960)0x4125c1f1dec8:[0x418035f80e1e]Portset_GetPort@vmkernel#nover+0x28e stack: 0x4125c1f1df28
2017-11-13T11:03:22.466Z cpu72:43960)0x4125c1f1df28:[0x418036009b11]Net_HaltCheck@vmkernel#nover+0x205 stack: 0x412500000001
2017-11-13T11:03:22.466Z cpu72:43960)0x4125c1f1df98:[0x41803605970e]CpuSched_VcpuHalt@vmkernel#nover+0x9a stack: 0x418000000000
2017-11-13T11:03:22.466Z cpu72:43960)0x4125c1f1dfe8:[0x418035ececa0]VMMVMKCall_Call@vmkernel#nover+0x48c stack: 0x0
2017-11-13T11:03:22.467Z cpu72:43960)0x418035ece2c4:[0xfffffffffc223baa]__module_desc_heap_max@<None>#<None>+0xc526918a stack: 0x0

(gdb) bt
#0 Panic_WithBacktrace (sbt=0x4108c01383c8, fmt=0x41803628e130 "PCPU %d: no heartbeat (%u/%u IPIs received)") at bora/vmkernel/main/panic.c:178
#1 0x000041803617819d in HeartbeatHandleLockup (data=<value optimized out>, timestamp=<value optimized out>) at bora/vmkernel/reliability/heartbeat.c:810
#2 HeartbeatCheckPCPU (data=<value optimized out>, timestamp=<value optimized out>) at bora/vmkernel/reliability/heartbeat.c:709
#3 Heartbeat_DetectCPULockups (data=<value optimized out>, timestamp=<value optimized out>) at bora/vmkernel/reliability/heartbeat.c:513
#4 0x0000418035ea8a30 in TimerBHHandlerLoop (unused=<value optimized out>) at bora/vmkernel/main/timer.c:2643
#5 Timer_BHHandler (unused=<value optimized out>) at bora/vmkernel/main/timer.c:2755
#6 0x0000418035e2e966 in BHCheckBegin (canReschedule=<value optimized out>) at bora/vmkernel/main/bh.c:1111
#7 BH_DrainAndDisableInterrupts (canReschedule=<value optimized out>) at bora/vmkernel/main/bh.c:1208
#8 0x0000418035eceada in VMMVMKCall_Call (function=43, args=<value optimized out>, eflagsBefore=0, status=<value optimized out>) at bora/vmkernel/main/vmmvmkcall.c:573
#9 0xfffffffffc223baa in ?? ()
#10 0x0000000000000000 in ?? ()
(gdb)

Resolution

It is known issue and has been fxied under vSphere ESXi 5.5 P10.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 5.5 Beta

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.5

Take Our Survey

Support Assistant