Why RHEV-H host becomes non-responsive after VM migration ?

Solution Verified - Updated -

Issue

  • Why does RHEV-H host become non-responsive after VM migration ?

  • Hypervisor Kernel panic with following traces:

An NMI occurred, but unable to determine source.
Kernel panic - not syncing: An NMI occurred, please see the Integrated Management Log for details.

Pid: 0, comm: swapper Not tainted 2.6.32-358.18.1.el6.x86_64 #1
Call Trace:
 <NMI>  [<ffffffff8150d668>] ? panic+0xa7/0x16f
 [<ffffffffa00404cd>] ? hpwdt_pretimeout+0x8d/0xbc [hpwdt]
 [<ffffffff81513875>] ? notifier_call_chain+0x55/0x80
 [<ffffffff815138da>] ? atomic_notifier_call_chain+0x1a/0x20
 [<ffffffff8109cc3e>] ? notify_die+0x2e/0x30
 [<ffffffff81511597>] ? do_nmi+0x217/0x340
 [<ffffffff81510e00>] ? nmi+0x20/0x30
 [<ffffffff81307665>] ? flush_tlb_others_ipi+0x11a/0x130
 <<EOE>>  [<ffffffff81307ac6>] ? native_flush_tlb_others+0x76/0x90

Environment

  • Red Hat Enterprise Virtualization 3.2
  • Red Hat Enterprise Linux 6.4 (HOST)
  • HP ProLiant BL465c G1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.