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-3.0. Manually network switch

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen-3.0. Manually network switch
From: Peter.Weiss@xxxxxxxxx
Date: Wed, 28 Dec 2005 15:55:45 +0100
Delivery-date: Wed, 28 Dec 2005 14:59:59 +0000
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/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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux)

since the effort for getting bonding interfaces to work is a bit to high for
our scenario, I'm developping some other solution for a better network

The dom0 has two physical network interfaces eth0, eth1. What I'd like to
create is a simple script that creates a second bridge with eth1 rather than
eth0. Replacing peth0 with eth1 does not work.

I'm a bit confused with the Xen network interface naming: vifn.0 corresponds
to the network interfaces of the XenU instances and vifn.1 corresponds to
the second network interfaces of the XenU instances, right?

vif0.0 seems to be some virtual interface that connects the bridge to Xen0,
but what's the peth0 interface and how do I create a peth1 interface?

# brctl show
bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              vif15.0
xenbr1          8000.000bcd681c68       no              eth1

If I remove the vif0.0 interfaces from xenbr0 I can't ping eth1 anymore.

How should this work?

TIA -- Peter

Peter.Weiss@xxxxxxxxx                         ConSol* Software GmbH
Phone  +49 89 45841-100                       Consulting & Solutions
Mobile +49 177 6040121                        Franziskanerstr. 38
http://www.consol.de                          D-81669 München

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Xen-3.0. Manually network switch, Peter . Weiss <=