> I've a set of machines (Network Engines, equivalent to IBM 
> 4000R's) which worked fine using the default configs for all 
> versions of Xen from 1.0 thru 2.0 testing, with both the 2.4 
> and 2.6 kernel; I'm trying to upgrade to 3.0.0 
> (xen-3.0-testing.hg changeset 8269), but am now having 
> trouble with PCI bus scanning -- only the first bus is found. 
> I've tried several permutations of nosmp, acpi=off, and 
> noapic on both the Xen and Linux command line, and have tried 
> various things like pci=noacpi,scanbus,lastbus=2 on the Linux 
> command line; no luck so far. (Without nosmp, acpi=off, and 
> noapic I tend to get hangs; I never needed to use those before.)
>
> Does anyone recognize this problem, and/or have any 
> suggestions for what to try next? I keep feeling like I'm 
> missing something obvious, but haven't spotted it so far. 
>
> Attached are the boot messages for:
> xen 2.0 with 2.4 kernel (works)
> xen 2.0 with 2.6.11 kernel (works)
> xen 3.0 with 2.6.12 kernel (panics)
>
> I'll keep poking at this (I desperately need to get it 
> working), and trying other permutations of kernels and boot 
> options; if anyone can provide any hints for how to debug 
> this I'd appreciate it a great deal.
Try diff'ing the output of a native 2.6.12 kernel booting vs. 2.6.12 on
xen. You can get both kernels from the xen test CD. You'll need a serial
line.
Best,
Ian 
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel