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: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Subject: Re: [Xen-devel] [1/3] [XEN] gnttab: Add new op unmap_and_replace
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Thu, 14 Jun 2007 12:01:48 +0100
Cc: Xen Development Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 14 Jun 2007 04:00:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4670F143.6040007@xxxxxxxxxx>
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: <C2949218.9045%Keir.Fraser@xxxxxxxxxxxx> <4670F143.6040007@xxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Thu, Jun 14, 2007 at 09:41:55AM +0200, Gerd Hoffmann wrote:
> Keir Fraser wrote:
> >On 6/6/07 08:54, "Gerd Hoffmann" <kraxel@xxxxxxxxxx> 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  -=| 

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