Re: [Xen-devel] Build vmlinuz-2.6.29-rc5-tip

[Jeremy Fitzhardinge <jeremy@xxxxxxxx>]

Pasi Kärkkäinen wrote:
> On Tue, Feb 17, 2009 at 10:40:54AM -0800, Jeremy Fitzhardinge wrote:
>   
> > Pasi Kärkkäinen wrote:
> >     
> > > On Tue, Feb 17, 2009 at 05:31:57AM -0800, Boris Derzhavets wrote:
> > >  
> > >       
> > > > Hardware config:-
> > > > C2D E8400, 8 GB RAM, ASUS P5K Premium/WIFI (Intel P35+Intel ICH9R),
> > > > 2x250 SATA Seagate Barracuda (no RAID). Bios settings for ICH9R - AHCI.
> > > > Details here:-
> > > > http://bderzhavets.wordpress.com/2009/02/17/setup-xen-unstable-dom0-via-2629-rc5-pv_ops-enabled-kernel-on-intel-sataahci/
> > > >
> > > >    
> > > >         
> > > Thanks!
> > >
> > > So it seems you're running 64 bit dom0 OS/hypervisor.. 
> > >
> > > 64 bit seems to work better atm than 32 bit.. 
> > >  
> > >       
> > I tend to focus on 64-bit, and Ian Campbell has been looking at 32-bit.  
> > In theory there shouldn't be all that much difference between them.  
> > There have been a few issues, but they're sharing 90+% of the code.  (In 
> > practice I'm interested in any bug reports, esp comparing 32 and 64-bit 
> > behaviour).
> >     
> I'm testing 32bit PAE dom0 on 32bit PAE hypervisor. 
>
> Today, with 2.6.29-rc5, I managed to boot my dom0 into login prompt! 
> I haven't been able to get this working earlier.. congratulations!
> I had to use 'noapic' dom0 kernel parameter though.. without 'noapic' I'm seeing
> the same IRQ problems with ata_piix than earlier.
>   
Hm, interesting.  One change I made in the last few days was making gsis 
map 1:1 with irqs, like the native kernel.  I wonder if that helps in 
your case.  That said, I'm not quite sure how its working with noapic; I 
would have thought that it wouldn't go through the Xen-hooked paths that 
way...
Oh, you're using ahci, not piix - and that works with noapic.  Hm, I 
should try that.
Can you start xend and a domain?

> My dom0 kernel config:
> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.29-rc5-tip-dom0
>
> My grub.conf:
> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/grub.conf
>
> Working dom0 bootlog with 'noapic':
> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-13-xen331-linux-2.6.29-rc5-noapic.txt
>   
What does your /proc/interrupts look like in this case?

> Failing dom0 bootlog (without 'noapic'):
> http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-12-xen331-linux-2.6.29-rc5.txt
>   
Do you think you could boot from a usb device or something and see if 
you can get /proc/interrupts for this as well?
Thanks,
   J

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