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>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] pci device not owned by pciback.
From: "Sergio Charpinel Jr." <sergiocharpinel@xxxxxxxxx>
Date: Thu, 29 Apr 2010 11:49:50 -0300
Cc:
Delivery-date: Thu, 29 Apr 2010 07:51:17 -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:content-type :content-transfer-encoding; bh=SX/v9bZnP0KUSN5ltrRM4+mY0P/eqBubjAYXyxGjoaw=; b=ur7c44rcSpqsXDNcPTluJ1cnfNwsNPUXq1C8gvnL/HV+goJfi3iuaDik3jdk9EPqwg iVU/ze/rtN+3/5e9vygkS1YZszWYLKz2evp+pIabCWRLP7LXv+/bSwOnh02hzQ64RC0J QBxB7JuU3NLLZwjRcbJpFZF9ieUK8scHZ4Aek=
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 :content-type:content-transfer-encoding; b=pXR/0O8ZnEO7KmTLpgKe7ytfTblEFGdJF6ngMX/B+Fsj4mR8+66YleqAUagWvgZYVt cX2GCFc3dujsx3ArbxR87ACUpXUZzwwTaCPod5+rfFB3HBvZ0qmW0SHoi23EzKqEYIh0 pIemZFDQst9bQyNaPdKhMwHyUdr7uyYwYonUs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1272551177.3080.66.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> <1272391712.3080.31.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <A5447537-D9FB-435C-84E9-B2293F263B19@xxxxxxxxx> <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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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 Roberto Charpinel Jr.

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