From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel P. Berrange" Subject: Re: [1/3] [XEN] gnttab: Add new op unmap_and_replace Date: Thu, 14 Jun 2007 12:01:48 +0100 Message-ID: <20070614110148.GA6320@redhat.com> References: <4670F143.6040007@redhat.com> Reply-To: "Daniel P. Berrange" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4670F143.6040007@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: Gerd Hoffmann Cc: Xen Development Mailing List , Keir Fraser , Herbert Xu List-Id: xen-devel@lists.xenproject.org On Thu, Jun 14, 2007 at 09:41:55AM +0200, Gerd Hoffmann wrote: > Keir Fraser wrote: > >On 6/6/07 08:54, "Gerd Hoffmann" wrote: > > > >>>Yeah, I think the key point was that whatever interface you end up using > >>>to configure the IP addr on should be eth0. > >>That trick is only needed if xend creates the bridge setup instead of > >>letting the distro network scripts do that. > > > >How would we do that in the distro-agnostic Xen tree? > > Documentation and sample config files? > > Sure, the down side is that "xend start" alone isn't enougth to make the > network fly. But that doesn't work that well, anything more complex > than "single ethernet interface" isn't covered by the scripts anyway. Even with a mere single ethernet interface, having 'xend start' mess with networking breaks anyone using iSCSI, AOE or NFS root/boot too. 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 -=|