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] Setting up virtual 'ethX' devices in Xen 3.4

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Setting up virtual 'ethX' devices in Xen 3.4
From: Digimer <linux@xxxxxxxxxxx>
Date: Fri, 10 Sep 2010 14:20:39 -0400
Delivery-date: Fri, 10 Sep 2010 11:21:57 -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
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100826 Thunderbird/3.0.7
Hi all,

  Up until now, we've been using Xen 3.0 on CentOS 5.x. Under this
setup, dom0 was given a virtual 'ethX' with the original 'ethX' (now
'pethX') IP address. Under this older config, neither 'pethX' or
'xenbrX' had an IP address. The logic was to keep traffic from the
domU's, through the bridge and out 'pethX' without dom0 seeing anything.

  This is particularly useful in our environment (2-node cluster using
DRBD to allow hot-migration and disaster recovery between nodes). Here
is what I am talking about, in graph form:


  I'd like to keep this setup, but it seems under Xen 3.4 this is no
longer the default configuration. I created a simple 'network-script' with:

dir=$(dirname "$0")
"$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0
"$dir/network-bridge" "$@" vifnum=N netdev=ethN bridge=xenbrN

  What else do I need to do to get the virtual copies of 'ethX' back on
my dom0?


E-Mail:         linux@xxxxxxxxxxx
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org

Xen-users mailing list

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