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


Re: [Xen-devel] vif0.0/veth0 or eth0

To: "Ewan Mellor" <ewan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] vif0.0/veth0 or eth0
From: "Nicholas Lee" <emptysands@xxxxxxxxx>
Date: Tue, 21 Feb 2006 09:13:44 +1300
Cc: Xen development list <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 20 Feb 2006 20:26:51 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sVftPtInsejCvGADgc7JTQskdGSeAZ//fhjQF4v4b2jsLaJMrdKZtJ/TN9nX+LitcXF29cqMC0upsZUxT9TeWrSzwjL6WSspl8rYNVSvGvWzXh81yjqlkUgCynHUCqSLqXdYXudgfmO/3QW7e0opygPuzkJaHcJfpw1XxC+Ymug=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20060220151942.GA16148@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <2b6116b30602191821n39c8b2f6y@xxxxxxxxxxxxxx> <43F9912D.40300@xxxxxxxxxxxx> <20060220151942.GA16148@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 21/02/06, Ewan Mellor <ewan@xxxxxxxxxxxxx> wrote:
> Indeed.  See also the final comments on bug #332.

Brillant!!! That solved by bridging problem completely.

Seems that xen 3.0 doesn't like networking set up at all like it was in 2.0.

ie. You can't just create your own bridge and add eth1 in host0 to
that bridge, then all the 2nd vifX.1 interfaces to it.

So the method that works it to configure eth0 and eth1 via the
standard methods. Then run the script as per

This is something that should be written about on XenNetworking and
probably included in the manual.

Only issue seems to be an interface alias eth1:0 didn't get
transfered. I'll explore that later, but this saves me trying
unstable. :D

Furthermore, I understand now that veth0 .. veth7 along with vif0.0 to
vif0.7 get created automatically by xen based on nloopbacks=8, which
is the default.

So its easy enough to follow the same process for xenbr2 to xenbr7, if
you so wish.

Nicholas Lee
gpg 8072 4F86 EDCD 4FC1 18EF  5BDD 07B0 9597 6D58 D70C

Xen-devel mailing list

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