From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [1/3] [XEN] gnttab: Add new op unmap_and_replace Date: Mon, 04 Jun 2007 16:12:22 +0200 Message-ID: <46641DC6.8080602@redhat.com> References: <20070604131247.GA17323@redhat.com> <20070604132915.GC17323@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070604132915.GC17323@redhat.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: "Daniel P. Berrange" Cc: Xen Development Mailing List , Keir Fraser , Herbert Xu List-Id: xen-devel@lists.xenproject.org Hi, > This will make it much easier for people who want to use bonding, or VLANs > and any other funky networking config in Dom0, and the same configs will > work for both Xen & KVM. Hence we wanted to have a generic 'eth0' and 'peth0' > rather than 'xenbr0' and 'eth0'. Of course there's plenty of other naming > schemes too, but figured since Xen already had the idea of a 'p' prefix for > identifying a physical device that seemed reasonable to keep. 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". cheers, Gerd