WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [1/3] [XEN] gnttab: Add new op unmap_and_replace

To: Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [1/3] [XEN] gnttab: Add new op unmap_and_replace
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Tue, 5 Jun 2007 17:36:19 +0100
Cc: Xen Development Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>, Gerd Hoffmann <kraxel@xxxxxxxxxx>, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 05 Jun 2007 09:34:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C28B4B2E.10161%keir@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: <46641DC6.8080602@xxxxxxxxxx> <C28B4B2E.10161%keir@xxxxxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Tue, Jun 05, 2007 at 05:17:34PM +0100, Keir Fraser wrote:
> On 4/6/07 15:12, "Gerd Hoffmann" <kraxel@xxxxxxxxxx> wrote:
> 
> > I'd rather name the things what they are.  Name the ethernet interface
> > eth0, name the bridge xenbr0 or virtbr0 or just br0.  Drop peth0.  The
> > only reason for the renaming was to trick the distro setup scripts by
> > doing "ifdown eth0; bridge-setup (with eth0 -> peth0 and veth0 -> eth0);
> > ifup eth0".
> 
> That trick still applies though, right? Just with xenbr0->eth0. The decision
> to use or not use this trick seems orthogonal to whether or not we have the
> veth0/vif0.0 loopback.

Yeah, I think the key point was that whatever interface you end up using
to configure the IP addr on should be eth0. So if the scripts configure
the IP on the bridge, then the bridge must be called eth0. This is so
that the admin's post-ifup scripts for eth0 get run correctly.  If you
further changed vif-bridge so that it kept the IP addr on the physical
interface instead, you could keep it called eth0 and name the bridge as
something else. Now that netloop isn't involved, either of those two
IP config scenarios should work fine.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel