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] RE: Simple network config question

To: Tait Clarridge <Tait.Clarridge@xxxxxxxxxxxx>, 'Jonathan Bayles' <jbayles@xxxxxxxxxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] RE: Simple network config question
From: Tait Clarridge <Tait.Clarridge@xxxxxxxxxxxx>
Date: Thu, 2 Jul 2009 13:11:55 -0400
Accept-language: en-US
Acceptlanguage: en-US
Delivery-date: Thu, 02 Jul 2009 10:14:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BE3E4AD392ABD547A384D0CAFD9E77E677DA780D@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <386FCF83D8086E4A89655E41CD3B53D3D1B2EA8A@rtexch01> <BE3E4AD392ABD547A384D0CAFD9E77E677DA780D@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acn7Mn8SEUEUloEcSt6VQo2gDGOATAABLPjwAAAk8bA=
Thread-topic: Simple network config question
> > Hey guys,
> >
> > Usually all my guests go out through various bridges connected to eth0, but 
> > I
> > came across a scenario where I need to connect one guest to a special
> > backend network. The network is connected to an access port on a switch via
> > eth2 on the xen server. If I set an IP on eth2 in the correct network it 
> > works
> just
> > fine. How can I share this connection up to a domU? I cant tell the 
> > switchport
> > to become a trunk and bridge out internally like I usually do. Any help is
> greatly
> > appreciated!!
> What you may want to try is bridging the connection on eth2 to something like
> xenbr2 and in the config file have a line that is:
> vif=['bridge=xenbr2']

EDIT: If you have a line in the domU configuration file that already has a vif 
stated, which will probably be the case (eg. vif=['bridge=xenbr0']) you can 
just add the following configuration for two network connections by doing 
something like: 


I have a similar setup for an iSCSI storage network where one of the NICs on 
the dom0 is connected to the iSCSI network and allows connectivity to the domU 
through a special network bridge "iscsibr0" which I add to the config file as I 
showed above.

Xen-users mailing list