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

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Simple network config question
From: Jonathan Bayles <jbayles@xxxxxxxxxxxxxx>
Date: Thu, 2 Jul 2009 12:31:05 -0400
Accept-language: en-US
Acceptlanguage: en-US
Delivery-date: Thu, 02 Jul 2009 09:33:29 -0700
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
Thread-index: Acn7Mn8SEUEUloEcSt6VQo2gDGOATA==
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 
Xen-users mailing list

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