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] How to deal with pciback?

To: foren@xxxxxxxxxxxxxx
Subject: Re: [Xen-users] How to deal with pciback?
From: "Todd Deshane" <deshantm@xxxxxxxxx>
Date: Tue, 12 Feb 2008 22:32:11 -0500
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 12 Feb 2008 19:32:44 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=qm6JQjgXHbM95fEIp4KhJgmV6drcr8VtQ8DEg5SeDxY=; b=S63DZFFkwfkjlwFfEhlMksQkMHpkG04CU6lm64xwPFN5i/+qVXRM3pADMeEHOoaDUC+48y4buL7wANAh/1jTHfCBV6J7VeXoV2cfutI1nyU1CW9hQvaYK64HFZ3Olf/2BVoIM9IvphZ0R0/DxYQPgq3Jzx+6u0PTUhHES/HrB1s=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=r1Ry34k+Zrag2hBY5wm08WwLtYTHpChmyrYoh5gJckmbaTnO+rLCTYtOeV877OQcLhJUGP10cj9z3+ydSu7t24uauSxseaqo57TmzYcfT40wZGe+bP6PZmplX3kS14sCtdgM8JH7h1zJpU1niIHYzsnPsfLEdF1ty/Q4dpjv9QQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <47AE1B56.5010402@xxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <47AE1B56.5010402@xxxxxxxxxxxxxx>
Reply-to: deshantm@xxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello,

On Feb 9, 2008 4:29 PM, Christian Scherer <foren@xxxxxxxxxxxxxx> wrote:
> Hello everybody,
>
> for just one week I try to install three servers on an OpenSuSE 10.3
> dom0 equipped with 4 NICs. One server is an OX using the onboard NIC via
> xenbr0. This server runs!! For my IPCop server I intended to use the
> three remaining NICs (Intel Pro100/S, 3Com 3C590, Realtek RTL-8139).
> These three NICs should be used natively by my IPCop. So I tried to use
> the pciback driver. I wrote a script containing "modprobe pciback" and
> the necessary unbind, new_slot, and bind commands. I also modified the
> configuration file for my IPCop domU by inserting the line
> pci=(´03:02.0´, ´03:03.0´, ´03:05.0´) and by removing the vif=...
> statement. When I start my IPCop domU I can't see the three NICs. It's
> also impossible to install the appropriate drivers manually.
>
> So I have two questions:
> 1. How to execute the bind and unbind commands automatically in dom0
> (bash script?, Who should call this bash script?)?
> 2. How to modify the domU configuration file?
>


The better approach is to use the following in your dom0 kernel
command line in grub:

 pciback.hide=(03:02.0) (03:03.0) (03:05.0)


Your dom0 configuration looks basically right.

I would use something like:

 pci=['03:02.0', '03:03.0', '03:05.0']

But your syntax might be equivalent, I am not sure.


In some cases you may also need pciback.permissive on your dom0 kernel
command line in grub.


Regards,
Todd




> Thank ou for your help.
>
> Christian
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

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

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