Kernel Panic:Hard LOCKUP occurs at vmx_vcpu_run

Solution Verified - Updated -

Issue

  • Hard LOCKUP occurs at vmx_vcpu_run.
Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 4
Pid: 4650, comm: qemu-kvm Tainted: G           ---------------- T 2.6.32-131.0.15.el6.x86_64 #1
Call Trace:
 <NMI>  [<ffffffff814dac28>] ? panic+0x78/0x143
 [<ffffffff810d649d>] ? watchdog_overflow_callback+0xcd/0xd0
 [<ffffffff81108b56>] ? __perf_event_overflow+0x116/0x290
 [<ffffffff81109149>] ? perf_event_overflow+0x19/0x20
 [<ffffffff8101dd56>] ? intel_pmu_handle_irq+0x316/0x550
 [<ffffffff814e06c6>] ? kprobe_exceptions_notify+0x16/0x430
 [<ffffffff814df1b8>] ? perf_event_nmi_handler+0x58/0xe0
 [<ffffffff814e0cf5>] ? notifier_call_chain+0x55/0x80
 [<ffffffff814e0d5a>] ? atomic_notifier_call_chain+0x1a/0x20
 [<ffffffff810940fe>] ? notify_die+0x2e/0x30
 [<ffffffff814de963>] ? do_nmi+0x173/0x2b0
 [<ffffffff814de270>] ? nmi+0x20/0x30
 [<ffffffffa01f57c7>] ? vmx_vcpu_run+0x3e7/0x800 [kvm_intel]
 <<EOE>>  [<ffffffffa01a6db5>] ? kvm_arch_vcpu_ioctl_run+0x345/0xec0 [kvm]
 [<ffffffff810a019e>] ? futex_wake+0x10e/0x120
 [<ffffffffa0191332>] ? kvm_vcpu_ioctl+0x522/0x670 [kvm]
 [<ffffffff8100bace>] ? common_interrupt+0xe/0x13
 [<ffffffff8100bace>] ? common_interrupt+0xe/0x13
 [<ffffffff8100bace>] ? common_interrupt+0xe/0x13
 [<ffffffff81184ee2>] ? vfs_ioctl+0x22/0xa0
 [<ffffffff81185060>] ? do_vfs_ioctl+0x60/0x580
 [<ffffffff811853aa>] ? do_vfs_ioctl+0x3aa/0x580
 [<ffffffff8110c3ea>] ? user_return_notifier_unregister+0x6a/0x70
 [<ffffffffa019dd53>] ? kvm_on_user_return+0x73/0x80 [kvm]
 [<ffffffff81185601>] ? sys_ioctl+0x81/0xa0
 [<ffffffff8100b172>] ? system_call_fastpath+0x16/0x1b

Environment

  • Red Hat Enterprise Linux 6
  • KVM host

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