From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robbie Dinn Subject: Re: vif0.0/veth0 or eth0 Date: Mon, 20 Feb 2006 09:51:41 +0000 Message-ID: <43F9912D.40300@microbus.com> References: <2b6116b30602191821n39c8b2f6y@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <2b6116b30602191821n39c8b2f6y@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Nicholas Lee Cc: Xen development list List-Id: xen-devel@lists.xenproject.org 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. quoting from /etc/xen/xend-config.sxp: > # It is possible to use the network-bridge script in more complicated > # scenarios, such as having two outgoing interfaces, with two bridges, and > # two fake interfaces per guest domain. To do things like this, write > # yourself a wrapper script, and call network-bridge from it, as appropriate. > # HTH Robbie Dinn