RE: [Xen-devel] [Patch] Fix the dom0 crash issue when "vcpus=0"in HVM guest configuration file

["Li, Xin B" <xin.b.li@xxxxxxxxx>]

>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Keir Fraser
>Sent: Friday, March 09, 2007 5:49 PM
>To: Han, Weidong; xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-devel] [Patch] Fix the dom0 crash issue when 
>"vcpus=0"in HVM guest configuration file
>
>
>
>
>On 9/3/07 02:47, "Han, Weidong" <weidong.han@xxxxxxxxx> wrote:
>
>> Dom0 would crash when "vcpus=0" in HVM guest configuration file. The
>> attached patch fixes the issue.
>
>If there is an underlying crash then I think this papers over 
>it rather than
>fixing it. Do you have a backtrace? If it's the BUG in 
>page_alloc.c then
>it's already fixed.
>
> -- Keir

Log for you:

(XEN) ----[ Xen-3.0-unstable  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    2
(XEN) RIP:    e008:[<ffff830000161564>] set_p2m_entry+0x174/0x1c0
(XEN) RFLAGS: 0000000000010206   CONTEXT: hypervisor
(XEN) rax: ffff830000257f28   rbx: ffff8300001c8080   rcx:
000000023725c067
(XEN) rdx: ffff830237207000   rsi: ffff830000257d58   rdi:
0000000000000000
(XEN) rbp: 0000000000000000   rsp: ffff830000257d38   r8:
0000000000106800
(XEN) r9:  0000000000000000   r10: 0000000000008dc9   r11:
0000000000000001
(XEN) r12: 000000000023725c   r13: 0000000000000000   r14:
000000000023725c
(XEN) r15: 0000000000002000   cr0: 000000008005003b   cr4:
00000000000026b0
(XEN) cr3: 000000001ccdc000   cr2: 00000000000018a0
(XEN) ds: 0000   es: 0000   fs: 0063   gs: 0000   ss: e010   cs: e008
(XEN) Xen stack trace from rsp=ffff830000257d38:
(XEN)    0000002700000200 0000000020000000 0000000000237207
ffff830237207000
(XEN)    0000000000000000 ffff8300001c8080 00000000001efa64
ffff830000257f28
(XEN)    0000000000000000 ffff830000161cae 0000000000000000
0000000000000001
(XEN)    0000000000000006 00000000438005e0 0000000000000000
ffff8300001c8080
(XEN)    ffff830000257e98 ffff8300001117c4 0000000000000000
0000000000000000
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000
(XEN)    0000000000000000 0000000000000001 ffff830000257f28
0000000080000002
(XEN)    000000000002692b 000000002692b167 ffff828400606eb8
ffff830000131b6e
(XEN)    0000000000000000 0000000000000000 0000000000000000
0000000000000000
(XEN)    000000000023725c 0000000000000000 000000002692b167
000000002692b067
(XEN)    ffff811555556760 0000000000000004 000000002692b167
ffff8300001320d4
(XEN)    ffff8300001c8080 00002aaaaac6c010 00000000000000a0
0000000000000000
(XEN)    0000000000000000 0000000000000206 00002aaaaac6c010
00000000000000a0
(XEN)    0000000000000000 0000000000000001 0000000000000206
ffff8300001d0080
(XEN)    00000000ffffffe7 00000000ffffffda 0000000000305000
0000000000000009
(XEN)    0000000000000009 ffff830000176102 0000000000000009
0000000000000009
(XEN)    0000000000305000 00000000ffffffda 00000000ffffffe7
ffff8801e38426c0
(XEN)    0000000000000282 0000000000000400 ffff8801e38426c0
0000000000000009
(XEN)    000000000000000c ffffffff8020618a 0000000000000000
00000000438005e0
(XEN)    0000000000000006 0000010000000000 ffffffff8020618a
000000000000e033
(XEN) Xen call trace:
(XEN)    [<ffff830000161564>] set_p2m_entry+0x174/0x1c0
(XEN)    [<ffff830000161cae>] guest_physmap_add_page+0x26e/0x2f0
(XEN)    [<ffff8300001117c4>] do_memory_op+0x834/0xe80
(XEN)    [<ffff830000131b6e>] get_page_from_l1e+0x30e/0x4b0
(XEN)    [<ffff8300001320d4>] mod_l1_entry+0x3c4/0x3f0
(XEN)    [<ffff830000176102>] syscall_enter+0x62/0x67
(XEN)
(XEN) Pagetable walk from 00000000000018a0:
(XEN)  L4[0x000] = 000000001ccf4067 00000000001db8f4
(XEN)  L3[0x000] = 000000001cd1c067 00000000001db91c
(XEN)  L2[0x000] = 0000000000000000 ffffffffffffffff
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 2:
(XEN) FATAL PAGE FAULT
(XEN) [error_code=0000]
(XEN) Faulting linear address: 00000000000018a0
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...

-Xin 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel