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] PCI bus scan failure on 3.0.0 testing

On Sat, 2006-01-21 at 20:45 +0000, Keir Fraser wrote:
> Yep, if you can find your way around the Linux PCI code a bit, it is 
> worth adding tracing to find out how it is finding buses 1 and 2. If 
> you can do that then it should be possible to backtrack and find out 
> where xenlinux is going wrong.
> 
>   -- Keir

I think the reason Linux is finding PCI buses 1 and 2 is because Steve
is using Xen 2.0 (which passes the bus numbers with PCI devices on them
explicitly to the Linux kernel via a hypercall since Xen hides the
bridges).

Steve, I'm not sure there's a way to know from your output if Linux
found the device you need for your hard drive or not (at least not
without compiling in some debug output), but I'd try double checking
that you've compiled in SCSI and the appropriate SCSI low-level driver
for your hardware (I didn't see a "SCSI subsystem initialized" line in
the log for the kernel that didn't work).

Ryan


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