Re: [Xen-devel] RE: [Xen-bugs] [Bug 122] Dom0 fails to boot on SLES 9 machines compiledwith x86 PAE mode ON

[Mark Williamson <mark.williamson@xxxxxxxxxxxx>]

> I think it's probably a property of the SLES 9 compiler used to compile
> Xen and Linux. I have two identical machines, one with SLES 9 and the
> other with RHEL 4, and the RHEL 4 box works fine. Also, I have a 3rd
> machine of a different model loaded with SLES 9 which is also not booting
> with PAE 'on'. That points to SLES 9.

Have you tried booting SLES with a kernel built using the RHEL compiler (or 
vice versa)?  Hopefully that'll confirm your hypothesis.

Cheers,
Mark

> Regards,
>
> David F Barrera
> Linux Technology Center
> Systems and Technology Group, IBM
>
> "The wisest men follow their own direction. "
>                                                         Euripides
>
>
>
>
> "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
> 08/03/2005 03:00 AM
>
> To
> David F Barrera/Austin/IBM@IBMUS, "xen-devel"
> <xen-devel@xxxxxxxxxxxxxxxxxxx>
> cc
> <ian.pratt@xxxxxxxxxxxx>
> Subject
> RE: [Xen-bugs] [Bug 122] Dom0 fails to boot on SLES 9 machines
> compiledwith x86 PAE mode ON
>
> > Subject: [Xen-bugs] [Bug 122] Dom0 fails to boot on SLES 9
> > machines compiledwith x86 PAE mode ON
>
> David, this crashes way too early to have anything to do with the SLES9
> filesystem.
>
> It must either be:
>  * a property of the SLES9 compiler used to compile xen and linux
>  * a property of the machine you're booting it on. (Are you using the
> exact same machine for your RHEL builds?)
>
> Please can you try an work out which.
>
> Thanks,
> Ian
>
> > (XEN) Xen-ELF header found:
> > 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000
>
> ,PAE=yes,LOADER=generic'
>
> > (XEN) PHYSICAL MEMORY ARRANGEMENT:
> > (XEN)  Dom0 alloc.:   08000000->10000000 (23732 pages to be allocated)
> > (XEN) VIRTUAL MEMORY ARRANGEMENT:
> > (XEN)  Loaded kernel: c0100000->c061b964
> > (XEN)  Init. ramdisk: c061c000->c061c000
> > (XEN)  Phys-Mach map: c061c000->c06532d0
> > (XEN)  Page tables:   c0654000->c065d000
> > (XEN)  Start info:    c065d000->c065e000
> > (XEN)  Boot stack:    c065e000->c065f000
> > (XEN)  TOTAL:         c0000000->c0800000
> > (XEN)  ENTRY ADDRESS: c0100000
> > (XEN) Scrubbing Free RAM: ......done.
> > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to
> > switch input to Xen).
> > <5>Linux version 2.6.12-xen0 (root@lamb22) (gcc version 3.3.3
> > (SuSE Linux)) #2 Tue Aug 2 17:34:21 PDT 2005 <6>BIOS-provided
> > physical RAM map:
> >  Xen: 0000000000100000 - 000000000dcb4000 (usable) <5>0MB
> > HIGHMEM available.
> > <5>220MB LOWMEM available.
> > (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
> > (XEN) CPU:    0
> > (XEN) EIP:    e019:[<c0117e0a>] ???
> > (XEN) EFLAGS: 00000206   CONTEXT: guest
> > (XEN) eax: 08660063   ebx: 08660063   ecx: 0065c300   edx: 00000000
> > (XEN) esi: c0660000   edi: 00001000   ebp: c0102000   esp: c057df30
> > (XEN) cr0: 8005003b   cr3: 08654000
> > (XEN) ds: e021   es: e021   fs: 0000   gs: e021   ss: e021   cs: e019
> > (XEN) Guest stack trace from esp=c057df30:
> > (XEN)    c065c304 00000003 c0117e0a 0001e019 00010206
> > 00000000 00001000 c058cbd9
> >
> >
> > (XEN)    c0660000 08660001 00000000 c058f380 c0102020
> > c0658000 00000001 00000101
> >
> >
> > (XEN)    c0654000 00000000 c0100000 00000010 00000000
> > c058cfaf c0586088 00100000
> >
> >
> > (XEN)    0055fb97 c048ce23 c0454704 c0100000 00000010
> > 00000000 c0586678 c057dff4
> >
> >
> > (XEN)    c05a4de0 00000080 00000000 00000000 ffffe000
> > c065d800 c05dac40 ffffe000
> >
> >
> > (XEN)    c065d800 c05dac40 00000000 c057e737 c057dff4
> > 00000000 00000000 00000000
> >
> >
> > (XEN)    00000000 c05db7c0 00020800 c010006c
> > (XEN) Domain 0 shutdown: rebooting machine.
> > (XEN) Reboot disabled on cmdline: require manual reset
> >
> >
> >
> >
> > ------- You are receiving this mail because: ------- You are
> > the assignee for the bug, or are watching the assignee.
> >
> > _______________________________________________
> > Xen-bugs mailing list
> > Xen-bugs@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-bugs

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