Re: xm create failure

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Fri, Mar 07, 2008 at 09:48:45AM +0200, Mihai Chelaru wrote:
> On Thursday 06 March 2008 17:40:57 you wrote:
> > Maybe it gives some details in xm dmesg ?
> 
> Hi,
> 
> Here is what I found in xm dmesg. Thanks for looking into this !
> 
> (XEN) traps.c:405:d50 Unhandled general protection fault fault/trap [#13] in 
> domain 50 on VCPU 0 [ec=0000]
> (XEN) domain_crash_sync called from entry.S (ff16641e)
> (XEN) Domain 50 (vcpu#0) crashed on cpu#3:
> (XEN) ----[ Xen-3.1.3  x86_32  debug=n  Not tainted ]----
> (XEN) CPU:    3
> (XEN) EIP:    e019:[<c0394759>]

Is it a custom kernel ? Next step would be to see where in the kernel
0xc0394759 is (use gdb l *(0xc0394759) or disas 0xc0394759),
and evenrtally do the same for the addresses printed in the stack trace.

-- 
Manuel Bouyer, LIP6, Universite Paris VI.           
Manuel.Bouyer%lip6.fr@localhost
     NetBSD: 26 ans d'experience feront toujours la difference
--