Bug 614308

Summary: Host crash when using virt-manager installing VM
Product: Red Hat Enterprise Linux 6 Reporter: Golita Yue <gyue>
Component: kernelAssignee: Gleb Natapov <gleb>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: medium    
Version: 6.0CC: knoel, lihuang, llim, michen, tburke
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-14 07:59:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Golita Yue 2010-07-14 05:46:44 UTC
Description of problem:
I was installing VM via virt-manager,the call trace display. 
The full dump file saved in my host.

crash> bt
PID: 20327  TASK: ffff8801663bcaa0  CPU: 1   COMMAND: "kvm-pit-wq"
 #0 [ffff880142577a20] machine_kexec at ffffffff810368bb
 #1 [ffff880142577a80] crash_kexec at ffffffff810b87f8
 #2 [ffff880142577b50] oops_end at ffffffff814db8d0
 #3 [ffff880142577b80] no_context at ffffffff8104545b
 #4 [ffff880142577bd0] __bad_area_nosemaphore at ffffffff810456e5
 #5 [ffff880142577c20] bad_area_nosemaphore at ffffffff810457b3
 #6 [ffff880142577c30] do_page_fault at ffffffff814dd3d8
 #7 [ffff880142577c80] page_fault at ffffffff814dac45
    [exception RIP: kvm_set_irq+92]
    RIP: ffffffffa02fc67c  RSP: ffff880142577d30  RFLAGS: 00010246
    RAX: 000000000000006b  RBX: 0000000000000000  RCX: 0000000000000001
    RDX: ffff880142577d40  RSI: 0000000000000000  RDI: ffff880142948000
    RBP: ffff880142577e00   R8: 0000000000000001   R9: 00000000ffffffff
    R10: 0000000000000000  R11: 0000000000000001  R12: ffff880126970788
    R13: ffff880142948000  R14: ffff880142577fd8  R15: 0000000000000001
    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
 #8 [ffff880142577e08] pit_do_work at ffffffffa031f1b4
 #9 [ffff880142577e38] worker_thread at ffffffff8108b6c0
#10 [ffff880142577ee8] kthread at ffffffff810909e6
#11 [ffff880142577f48] kernel_thread at ffffffff810141ca
crash> quit

Version-Release number of selected component (if applicable):
kernel-2.6.32-44.el6.x86_64

How reproducible:


Steps to Reproduce:
1. use virt-manager install VM
2. There are 3 VM are running, one has 7603MB vmem,the other has 2G vmem (the host has 8G mem)
3.
  
Actual results:
Pid: 20327, comm: kvm-pit-wq Not tainted 2.6.32-44.el6.x86_64 #1 HP Compaq dc5850 Microtower
RIP: 0010:[<ffffffffa02fc67c>]  [<ffffffffa02fc67c>] kvm_set_irq+0x5c/0x140 [kvm]
RSP: 0018:ffff880142577d30  EFLAGS: 00010246
RAX: 000000000000006b RBX: 0000000000000000 RCX: 0000000000000001
RDX: ffff880142577d40 RSI: 0000000000000000 RDI: ffff880142948000
RBP: ffff880142577e00 R08: 0000000000000001 R09: 00000000ffffffff
R10: 0000000000000000 R11: 0000000000000001 R12: ffff880126970788
R13: ffff880142948000 R14: ffff880142577fd8 R15: 0000000000000001
FS:  00007f98f08c67c0(0000) GS:ffff880028280000(0000) knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 000000000000006b CR3: 00000001f537e000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process kvm-pit-wq (pid: 20327, threadinfo ffff880142576000, task ffff8801663bcaa0)
Stack:
 ffff880142577d70 0000000181058f92 0000000000000000 0000000000016840
<0> 0000000000000000 ffff880214b98680 0000000000000000 0000000000000000
<0> ffff880142577e30 ffffffff814d7f86 0000000000000000 0000000000000000
Call Trace:
 [<ffffffff814d7f86>] ? thread_return+0x4e/0x778
 [<ffffffffa031f1b4>] pit_do_work+0x74/0xf0 [kvm]
 [<ffffffffa031f140>] ? pit_do_work+0x0/0xf0 [kvm]
 [<ffffffff8108b6c0>] worker_thread+0x170/0x2a0
 [<ffffffff81090d50>] ? autoremove_wake_function+0x0/0x40
 [<ffffffff8108b550>] ? worker_thread+0x0/0x2a0
 [<ffffffff810909e6>] kthread+0x96/0xa0
 [<ffffffff810141ca>] child_rip+0xa/0x20
 [<ffffffff81090950>] ? kthread+0x0/0xa0
 [<ffffffff810141c0>] ? child_rip+0x0/0x20
Code: d8 00 00 00 49 8b 85 f0 23 00 00 3b 98 28 01 00 00 73 64 89 db 48 8b 84 d8 30 01 00 00 48 85 c0 74 55 48 8d 95 40 ff ff ff 31 db <48> 8b 08 83 c3 01 0f 18 09 48 8b 48 e0 48 89 0a 48 8b 48 e8 48 
RIP  [<ffffffffa02fc67c>] kvm_set_irq+0x5c/0x140 [kvm]
 RSP <ffff880142577d30>
CR2: 000000000000006b


crash> bt
PID: 20327  TASK: ffff8801663bcaa0  CPU: 1   COMMAND: "kvm-pit-wq"
 #0 [ffff880142577a20] machine_kexec at ffffffff810368bb
 #1 [ffff880142577a80] crash_kexec at ffffffff810b87f8
 #2 [ffff880142577b50] oops_end at ffffffff814db8d0
 #3 [ffff880142577b80] no_context at ffffffff8104545b
 #4 [ffff880142577bd0] __bad_area_nosemaphore at ffffffff810456e5
 #5 [ffff880142577c20] bad_area_nosemaphore at ffffffff810457b3
 #6 [ffff880142577c30] do_page_fault at ffffffff814dd3d8
 #7 [ffff880142577c80] page_fault at ffffffff814dac45
    [exception RIP: kvm_set_irq+92]
    RIP: ffffffffa02fc67c  RSP: ffff880142577d30  RFLAGS: 00010246
    RAX: 000000000000006b  RBX: 0000000000000000  RCX: 0000000000000001
    RDX: ffff880142577d40  RSI: 0000000000000000  RDI: ffff880142948000
    RBP: ffff880142577e00   R8: 0000000000000001   R9: 00000000ffffffff
    R10: 0000000000000000  R11: 0000000000000001  R12: ffff880126970788
    R13: ffff880142948000  R14: ffff880142577fd8  R15: 0000000000000001
    ORIG_RAX: ffffffffffffffff  CS: 0010  SS: 0018
 #8 [ffff880142577e08] pit_do_work at ffffffffa031f1b4
 #9 [ffff880142577e38] worker_thread at ffffffff8108b6c0
#10 [ffff880142577ee8] kthread at ffffffff810909e6
#11 [ffff880142577f48] kernel_thread at ffffffff810141ca
crash> quit


Expected results:
no any error

Additional info:
The full dump file saved in my host, if needed, you can access my host to find some useful information.

Comment 2 Lawrence Lim 2010-07-14 07:32:57 UTC
Is it 100% reproducible??

Comment 3 Golita Yue 2010-07-14 07:47:58 UTC
Hit this bug twice during daily testing this week. 
I just install VM by virt-manager and there are 3-4 VMs running at same time,then the host crashed.

Comment 4 Gleb Natapov 2010-07-14 07:59:45 UTC

*** This bug has been marked as a duplicate of bug 612648 ***