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/
Home Products Support Community News


[Xen-users] XEN and NICS

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] XEN and NICS
From: "Hans Pfeil" <HPfeil@xxxxxxx>
Date: Tue, 17 Feb 2009 15:53:53 -0600
Delivery-date: Tue, 17 Feb 2009 13:54:43 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hey all, running sles10sp2 with Xen running from Novell.  My goal is to get 
each virtual server its own nic.  Here is what I have:

-   eth0 (onboard broadcom) is the nic dom0 is using, this has an IP address
-   eth1 (onboard broadcom) does not have an IP address, nothing connected
-   eth2-9 (two quad-port intel nics) these do not have an IP address.
-   All nics will be on the same subnet.

So, with the above shouldn't my bridge script be as follows:

dir=$(dirname $0)
"${dir}/network-bridge" "$@" vifnum=2 netdev=eth2 bridge=eth2
"${dir}/network-bridge" "$@" vifnum=3 netdev=eth3 bridge=eth3

and so on.....

Wouldn't adding eth0 to the script mess things up?  Shouldn't I leave eth0 and 
eth1 out of the script?


Xen-users mailing list

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