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


Re: [Xen-devel] nfsroot and brige

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] nfsroot and brige
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 13 Jan 2005 12:04:16 +0000
Cc: "Leigh Brown" <leigh@xxxxxxxxxxxxx>, "Ronald G. Minnich" <rminnich@xxxxxxxx>, "Ian Pratt" <m+ian.pratt@xxxxxxxxxxxx>, "Adam Sulmicki" <adam@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 13 Jan 2005 12:08:02 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: Your message of "Thu, 13 Jan 2005 09:33:43 GMT." <E1Cp1MP-00070X-00@xxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> > One tweak I do make is to set up the bridge in Dom0 first.  I'd
> > be happy if bridge support was changed to require a pre-existing
> > bridge...
> The bridge config scripts are quite simple. The intention is that you
> customise them for your site. I'll leave example bridge scripts even
> though the default will change to using routing.
> I'll send a message here to describe how to switch between bridging
> and routing.

I've checked in new routing scripts to 2.0-testing and unstable
trees. Note that I have *not* changed the default behaviour, which is
to bridge VIFs at the MAC level.

If you want to route instead of bridge:

 1. Edit /etc/xen/xend-config.sxp. Delete the lines referring to
    bridging, and instead uncomment the lines referring to routing.

 2. You may want to edit /etc/xen/scripts/network-route and
    /etc/xen/scripts/vif-route. The former currently enables IP
    forwarding when xend is started; the latter brings up the VIF
    with a dummy IP address, installs a /32 routing rule (the IP
    address is grabbed from the config file as described in step 3),
    and enables proxy ARP.

 3. You will need to edit your VM config file to include a 'vif list'
    containing the IP address of each VIF you are configuring. i.e.,
    the list must look at least something like:
    vif = [ 'ip=' ]
    (This just extends the existing 'vif' syntax, but a lot of people
    probably have been able to avoid needing to specify any vif
    details so far).

Let me know how you get on!

 -- Keir

The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
Xen-devel mailing list