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

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

[David F Barrera]

Ian Pratt wrote:

> 
>  
>
>>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.
>  
>
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 with PAE 'on'. 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.

>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@lists.xensource.com
>>http://lists.xensource.com/xen-bugs
>>
>>    
>>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>  
>

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

[Ian Pratt]

 
> 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. 

Is it still the case with the very latest tree, i.e. where the default
build is pentiumpro rather than pentium4?

Ian

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

[David F Barrera]

Ian Pratt wrote:

> 
>  
>
>>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. 
>>    
>>
>
>Is it still the case with the very latest tree, i.e. where the default
>build is pentiumpro rather than pentium4?
>  
>
We haven't tried it yet this morning. 

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

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

[Natasha Jarymowycz]

On Wed, 3 Aug 2005 15:40:38 +0100, Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> wrote:

>
>> 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.
>
> Is it still the case with the very latest tree, i.e. where the default
> build is pentiumpro rather than pentium4?


I'm seeing this on an x440 with SLES 9, using changeset 6003.
Interestingly, I make it past this point if I specify mem=4G at boot.

The crash happens very early on when booting Xen so I don't
think Linux can be the problem.  I tossed some printk's into
paging_init() (that's where the last line of output came
 from in the original boot log) to see if it dies in that function.

It seems to die somewhere in this code as I see the first printk message,
but not the last as it is about to exit:

xen/arch/x86/x86_32/mm.c, starting at line 95:
     printk("paging_init: about to allocate and map machine-to-phys table\n");
     /*
      * Allocate and map the machine-to-phys table and create read-only mapping
      * of MPT for guest-OS use.  Without PAE we'll end up with one 4MB page,
      * with PAE we'll allocate 2MB pages depending on the amount of memory
      * installed, but at least 4MB to cover 4GB address space.  This is needed
      * to make PCI I/O memory address lookups work in guests.
      */
     if ( (mpt_size = max_page * 4) < (4*1024*1024) )
         mpt_size = 4*1024*1024;
     for ( i = 0; i < (mpt_size >> L2_PAGETABLE_SHIFT); i++ )
     {
         if ( (pg = alloc_domheap_pages(NULL, PAGETABLE_ORDER, 0)) == NULL )
             panic("Not enough memory to bootstrap Xen.\n");
         idle_pg_table_l2[l2_linear_offset(RDWR_MPT_VIRT_START) + i] =
             l2e_from_page(pg, PAGE_HYPERVISOR | _PAGE_PSE);
         idle_pg_table_l2[l2_linear_offset(RO_MPT_VIRT_START) + i] =
             l2e_from_page(pg, (__PAGE_HYPERVISOR | _PAGE_PSE) & ~_PAGE_RW);
     }
     memset((void *)RDWR_MPT_VIRT_START, 0x55, mpt_size);

     /* Create page tables for ioremap(). */
     for ( i = 0; i < (IOREMAP_MBYTES >> (L2_PAGETABLE_SHIFT - 20)); i++ )
     {
         ioremap_pt = alloc_xenheap_page();
         clear_page(ioremap_pt);
         idle_pg_table_l2[l2_linear_offset(IOREMAP_VIRT_START) + i] =
             l2e_from_page(virt_to_page(ioremap_pt), __PAGE_HYPERVISOR);
     }

     /* Set up mapping cache for domain pages. */
     mapcache_order = get_order(MAPCACHE_MBYTES << (20 - PAGETABLE_ORDER));
     mapcache = alloc_xenheap_pages(mapcache_order);
     memset(mapcache, 0, PAGE_SIZE << mapcache_order);
     for ( i = 0; i < (MAPCACHE_MBYTES >> (L2_PAGETABLE_SHIFT - 20)); i++ )
         idle_pg_table_l2[l2_linear_offset(MAPCACHE_VIRT_START) + i] =
             l2e_from_page(virt_to_page(mapcache) + i, __PAGE_HYPERVISOR);

    printk("paging_init: exiting function\n");
}

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

[Keir Fraser]

On 3 Aug 2005, at 16:01, Natasha Jarymowycz wrote:

> I'm seeing this on an x440 with SLES 9, using changeset 6003.
> Interestingly, I make it past this point if I specify mem=4G at boot.
>
> The crash happens very early on when booting Xen so I don't
> think Linux can be the problem.  I tossed some printk's into
> paging_init() (that's where the last line of output came
> from in the original boot log) to see if it dies in that function.
>
> It seems to die somewhere in this code as I see the first printk 
> message,
> but not the last as it is about to exit:

I strongly doubt anyone has tested PAE Xen on a >4GB machine. You are 
trailblazing. ;-)

I think Gerd's test box isn't even SMP.

We have a 8GB box we could do some testing on...

  -- Keir

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

[Gerd Knorr]

Keir Fraser <Keir.Fraser@cl.cam.ac.uk> writes:

> I strongly doubt anyone has tested PAE Xen on a >4GB machine. You are
> trailblazing. ;-)
> 
> I think Gerd's test box isn't even SMP.

It's hyperthreaded, so it's SMP, but has 1GB only.

I'll look at the 4GB issues soon, I've got access to a big machine
with >4GB of memory in the suse hw labs, busy setting it up right now.
Stay tuned, most likely some patches show up on the list next days ;)

  Gerd

-- 
panic("it works"); /* avoid being flooded with debug messages */

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

[Paul Larson]

[-- Attachment #1.1: Type: text/plain, Size: 974 bytes --]

On Wed, 2005-08-03 at 16:09 +0100, Keir Fraser wrote:
> On 3 Aug 2005, at 16:01, Natasha Jarymowycz wrote:
> 
> > I'm seeing this on an x440 with SLES 9, using changeset 6003.
> > Interestingly, I make it past this point if I specify mem=4G at boot.
> >
> > The crash happens very early on when booting Xen so I don't
> > think Linux can be the problem.  I tossed some printk's into
> > paging_init() (that's where the last line of output came
> > from in the original boot log) to see if it dies in that function.
> >
> > It seems to die somewhere in this code as I see the first printk 
> > message,
> > but not the last as it is about to exit:
> 
> I strongly doubt anyone has tested PAE Xen on a >4GB machine. You are 
> trailblazing. ;-)
Not true, just not successfully yet.  I have a 4G and a 6G box I'm
testing PAE with right now, blocked on bug 135 though.

-- 
Thanks,
Paul Larson
plars@linuxtestproject.org
http://www.linuxtestproject.org

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

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

[Mark Williamson]

> 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@cl.cam.ac.uk>
> 08/03/2005 03:00 AM
>
> To
> David F Barrera/Austin/IBM@IBMUS, "xen-devel"
> <xen-devel@lists.xensource.com>
> cc
> <ian.pratt@cl.cam.ac.uk>
> 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@lists.xensource.com
> > http://lists.xensource.com/xen-bugs

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

[Anthony Liguori]

David F Barrera wrote:

>
> 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.

This would be easy to verify by simply compiling the Linux and Xen on 
the RHEL system, then taking those images and trying to boot the SLES9 
system with it.  If it works, then it's a compilation issue.

I have a feeling there's something else going on here though.

Regards,

Anthony Liguori

> 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@cl.cam.ac.uk>*
>
> 08/03/2005 03:00 AM
>
> 	
> To
> 	David F Barrera/Austin/IBM@IBMUS, "xen-devel" 
> <xen-devel@lists.xensource.com>
> cc
> 	<ian.pratt@cl.cam.ac.uk>
> 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@lists.xensource.com
> > http://lists.xensource.com/xen-bugs
> >
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>  
>