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: Robbie Dinn <robbie@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] vif0.0/veth0 or eth0
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Mon, 20 Feb 2006 15:19:42 +0000
Cc: Xen development list <xen-devel@xxxxxxxxxxxxxxxxxxx>, Nicholas Lee <emptysands@xxxxxxxxx>
Delivery-date: Mon, 20 Feb 2006 15:34:37 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43F9912D.40300@xxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Feb 20, 2006 at 09:51:41AM +0000, Robbie Dinn wrote:

> Nicholas Lee wrote:
> >When does vif0.0 get created?
> don't know
> >
> >Is there some shell magic?
> Are you using bridging?
> If so, I think I know this!
> look for shell function 'op_start' in file /etc/xen/scripts/network-bridge
> >
> >I'm trying to figure out how to do a similar peth1/veth1 split for eth1.
> Maybe it is as simple as replacing /etc/xen/scripts/network-bridge
> with a wrapper that invokes the original /etc/xen/scripts/network-bridge
> twice, each time with different values for environment variables
> vifnum, bridge, and netdev. Those environment variables are documented
> at the top of /etc/xen/scripts/network-bridge.

Indeed.  See also the final comments on bug #332.


Xen-devel mailing list

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