|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] domU crashing, trying to determine why
On Sat, Jan 01, 2011 at 02:16:55PM -0500, Micah Anderson wrote:
>
> I'm having a domU that is regularly crashing, without any obvious reason
> why. I set 'on_crash=preserve' to try and get a crash to try and get
> some clues, but what I got doesn't too obvious to me. I was hoping
> someone here would be able to give me some clues.
>
> Thanks for any clues anyone can give! Here is what I managed to eke out:
>
> root@guillemot:/etc/xen# /usr/lib/xen-3.2-1/bin/xenctx -s
> /boot/System.map-2.6.26-2-xen-686 11 0
So the domU has only 1 vcpu?
-- Pasi
> eip: c01013a7 hypercall_page+0x3a7 flags: 00001246 i z p
> esp: c0389fbc
> eax: 00000000 ebx: 00000001 ecx: 00000000 edx: c0389fc8
> esi: 00000000 edi: 00000000 ebp: 00000000
> cs: 00000061 ds: 0000007b fs: 000000d8 gs: 00000000
>
> Stack:
> c0105f52 ffffffff 00000000 c06ca9dd 0009cf8a 00000000 00000020 ffffffff
> c01028ab c0102810 00000020 c1631000 00000000 c038f88b c03ac580 0702080b
> 00000000
>
> Code:
> cc cc cc cc cc cc cc cc cc cc cc cc cc cc b8 1d 00 00 00 cd 82 <c3> cc cc cc
> cc cc cc cc cc cc cc
>
> Call Trace:
> [<c01013a7>] hypercall_page+0x3a7 <--
> [<c0105f52>] xen_safe_halt+0x9f
> [<c01028ab>] xen_idle+0x1b
> [<c0102810>] cpu_idle+0xa8
> [<c038f88b>] start_kernel+0x2f5
> root@guillemot:/etc/xen# /usr/lib/xen-3.2-1/bin/xenctx -s
> /boot/System.map-2.6.26-2-xen-686 11 1
> eip: c0170f39 file_kill+0x27 flags: 00001202 i nz
> esp: e74cbf2c
> eax: ec825e98 ebx: d7033a80 ecx: ee07207f edx: e7672e80
> esi: d7033a80 edi: ed3942c0 ebp: ed396be8
> cs: 00000061 ds: 0000007b fs: 000000d8 gs: 00000000
>
> Stack:
> 00000010 c01710ae ed420f00 e81b3a78 e82d5cfc e7218b00 e74ca000 c016080d
> c123f020 e81b3a78 c01608e7 000001e8 c123f020 e7218b00 e7218b4c 00000000
> c011c723 00000000 e59bba80 c01214aa 00000001 e7447a80 e7688580 00000000
> e76885c0 00000000 ed4ebd00 00000000 e74ca000 c0121998 00000000 00000000
>
> Code:
> 13 8b 43 04 89 42 04 89 10 89 5b 04 89 1b f0 fe 05 40 42 38 c0 <0f> b7 15 40
> 42 38 c0 38 f2 0f 95
>
> Call Trace:
> [<c0170f39>] file_kill+0x27 <--
> [<c01710ae>] __fput+0xd2
> [<c016080d>] remove_vma+0x25
> [<c01608e7>] exit_mmap+0xbc
> [<c011c723>] mmput+0x24
> [<c01214aa>] do_exit+0x1ad
> [<c0121998>] do_group_exit+0x94
> [<c01219ce>] sys_exit_group+0xd
> [<c0103f76>] syscall_call+0x7
> [<c02c0000>] zone_wait_table_init+0x47
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] domU crashing, trying to determine why, Micah Anderson
- Re: [Xen-devel] domU crashing, trying to determine why,
Pasi Kärkkäinen <=
- Re: [Xen-devel] domU crashing, trying to determine why, micah anderson
- Re: [Xen-devel] domU crashing, trying to determine why, Pasi Kärkkäinen
- Re: [Xen-devel] domU crashing, trying to determine why, micah anderson
- Re: [Xen-devel] domU crashing, trying to determine why, Pasi Kärkkäinen
- Re: [Xen-devel] domU crashing, trying to determine why, micah anderson
- Re: [Xen-devel] domU crashing, trying to determine why, Pasi Kärkkäinen
- Re: [Xen-devel] domU crashing, trying to determine why, Konrad Rzeszutek Wilk
- Re: [Xen-devel] domU crashing, trying to determine why, Ian Campbell
- Re: [Xen-devel] domU crashing, trying to determine why, micah anderson
- Re: [Xen-devel] domU crashing, trying to determine why, Ian Campbell
|
|
|
|
|