WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] domU crashing, trying to determine why

On Fri, Jan 14, 2011 at 12:31:22PM -0500, micah anderson wrote:
> On Mon, 3 Jan 2011 12:14:25 -0500, Konrad Rzeszutek Wilk 
> <konrad.wilk@xxxxxxxxxx> wrote:
> > On Mon, Jan 03, 2011 at 12:03:34PM -0500, micah anderson wrote:
> > > On Mon, 3 Jan 2011 11:40:31 -0500, Konrad Rzeszutek Wilk 
> > > <konrad.wilk@xxxxxxxxxx> wrote:
> > > > > > I've got this setup:
> > > > > > 
> > > > > > vcpus=2
> > > > > > cpus=[1,3]
> > > > 
> > > > Is there anything in the Xen hypervisor ring buffer? You might need to 
> > > > enable the 
> > > > full logging of the guest and dom0 to get anything there.
> > > 
> > > How do I get at the ring buffer, and what specifically should I enable
> > 
> > 'xm dmesg'
> 
> (XEN) mm.c:645:d2 Non-privileged (2) attempt to map I/O space 000000f0

Hmm, that should not happen anymore, as there are is a bunch of
code guarding domains from trying to touch 0->0x100. Unless your guest
has the old stuff.

> (XEN) traps.c:2544: GPF (0068): ff1886c2 -> ff1887c9
> (XEN) domain_crash_sync called from entry.S (ff188600)
> (XEN) Domain 2 (vcpu#1) crashed on cpu#3:
> (XEN) ----[ Xen-3.2-1  x86_32p  debug=n  Tainted:    C ]----

Ugh, ancient hypervisor.

> (XEN) CPU:    3
> (XEN) EIP:    0061:[<c01013a7>]

Now use gdb to lookup that EIP value. Or use your guest System.map
to see what function this could map too.

> (XEN) EFLAGS: 00000246   CONTEXT: guest
> (XEN) eax: 00000000   ebx: 00000001   ecx: 00000000   edx: ed447f90
> (XEN) esi: 00000001   edi: 00000001   ebp: 00000000   esp: ed447f84
> (XEN) cr0: 8005003b   cr4: 000006f0   cr3: 00bdac80   cr2: 095346dc
> (XEN) ds: 007b   es: 007b   fs: 00d8   gs: 0000   ss: 0069   cs: 0061
> (XEN) Guest stack trace from esp=ed447f84:
> (XEN)    c0105f52 ffffffff 00000001 673bfa5d 0002dba1 00000000 00000000 
> ffffffff
> (XEN)    c01028ab c0102810 00000000 00000000 00000000 00000000 00000000 
> 00000000

And potentially c01028ab  c0105f52 .. 
> (XEN)    00000000 00000000 00000000 00000000 00000000 00000000 000000d8 
> 00000000
> (XEN)    00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 



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