[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] pci device not owned by pciback.


  • To: James Pifer <jep@xxxxxxxxxxxxxxxx>
  • From: "Sergio Charpinel Jr." <sergiocharpinel@xxxxxxxxx>
  • Date: Mon, 3 May 2010 08:47:53 -0300
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 03 May 2010 04:49:09 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=TWiUD2IvB3CqRCatbgPughZelKblwr4bQPdjhyBwE00NKksUGAmJOXhgz3iI8rarWa ZFMo8IQ4RAQPmLa9ziW8NWDpdGmh3i7XebBv4tKPbyfqeKTWbAm6z8zHK+ufZ1K2iIC8 e9rJ4mGUxK064EbKnJZrybSq66gSzW1Ech1mE=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Ok James,

I think that you forgot some steps. Do this, renaming your pci device,
initrd and kernel names:

# echo "options pciback hide=(41:00.0)" >> /etc/modprobe.conf
# cd /boot
# cp initrd-2.6.27.19-5-xen ïinitrd-2.6.27.19-5-xen.save
# mkinitrd -f --with=pciback --preload=pciback initrd-2.6.27.19-5-xen
2.6.27.19-5-xen

You could also try to specify your SCSI driver name in
/etc/modules.conf, before making the image.

Hope this helps.

2010/4/29 James Pifer <jep@xxxxxxxxxxxxxxxx>:
> 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@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>



-- 
Sergio Roberto Charpinel Jr.

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.