[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xen-users
Subject:    Re: [Xen-users] pci device not owned by pciback.
From:       James Pifer <jep () obrien-pifer ! com>
Date:       2010-04-29 15:09:56
Message-ID: 1272553796.3080.75.camel () storage ! obrien-pifer ! com
[Download RAW message or body]

On Thu, 2010-04-29 at 11:49 -0300, Sergio Charpinel Jr. wrote:
> James,
> Taking a look at mkinitrd manpage:
> --preload=moduleLoad the module module in the initial ramdisk image.
> The module gets loaded before any SCSI modules which are specified in
> /etc/modules.conf. This option may be used as many times as necessary.
> 
> mkinitrd --preload=pciback IMAGENAME KERNELVERSION
> 
> Specify in /etc/modules.conf your SCSI driver. Your pciback options
> should be in modprobe.conf as well. Maybe I'm missing some point, but
> you should try this.
> 
> If it do not work, maybe you can think in recompile your kernel with
> pciback inside your kernel.
> 
> Hope this helps.


Sergio,

Thanks for the response. I don't think you're really missing anything,
except my lack of experience in this area. You say "you should try
this". I'm not exactly sure what to try. 

So with the system booted up would I do the following steps?

# cp initrd-2.6.27.19-5-xen initrd-2.6.27.19-5-xen.save
# mkinitrd --preload=pciback initrd-2.6.27.19-5-xen 2.6.27.19-5-xen

Then reboot after modules.conf is updated?

Recompiling the kernel is not something I really want to get into. We're
looking at having a lot of servers that need to be able to do this. 

Thanks,
James


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

[prev in list] [next in list] [prev in thread] [next in thread]