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-users

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

To: James Pifer <jep@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] pci device not owned by pciback.
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
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=CB0RDrt4NV2oVKR5It3xbZy1awdiLFraVmiTtDTEvG8=; b=oiLyeXepy5r0yUYFLzFlSo+VUH/BbaCfX2Jetnpn0IFNiiHG9GuzUuhrgi2VCI8Zc2 LtYiFQK2eAK8q+hIdRSmrzgrSJFCAhI9x8mxSHwouD5QjDOorBt8vIusdB7kjAYbimsf WrkDmNR71ci4hmz/J+fE+C+0cA+fSKXkBkFqE=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1272553796.3080.75.camel@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1272373556.19411.47.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <1272393974.3080.37.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <o2nfca1d54a1004280749u46e92074o5ceb2b86dc1801b@xxxxxxxxxxxxxx> <1272476279.3080.46.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <1272481985.3080.50.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <o2yfca1d54a1004281514wa895227cg8a4d92d01fa78375@xxxxxxxxxxxxxx> <1272501761.3080.52.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <1272551177.3080.66.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <q2yfca1d54a1004290749ha5bd37abt26a3717df33429ef@xxxxxxxxxxxxxx> <1272553796.3080.75.camel@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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

<Prev in Thread] Current Thread [Next in Thread>