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] xen 2.0.1, 2.4.27, 2.6.9, non-bridge

To: Adam Heath <doogie@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xen 2.0.1, 2.4.27, 2.6.9, non-bridge
From: Derrik Pates <dpates@xxxxxxxxxx>
Date: Sat, 01 Jan 2005 00:57:46 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 01 Jan 2005 06:01:14 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.58.0412312326240.21792@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <Pine.LNX.4.58.0412312326240.21792@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.9 (X11/20041124)
Adam Heath wrote:
For 2.0, the way the bridge is configured breaks the existing networking, upon
which nfsroot is running.

I don't see how. The only thing I've run into is the fact that the included script that's supposed to configure up xen-br0 doesn't transfer the config properly to xen-br0 from eth0, and doesn't change eth0's IP to 0.0.0.0; I'm intending to just remove the script from my Xen systems, and just configure the bridge device the right way from the word go.

However, with *both* 2.4.27 *and* 2.6.9, I am getting kernel panics.  I have
not run the oops on 2.4 thru ksymoops.  The built in oops decode logic in
2.6.9 shows a null pointer in the arp_send routine.

Well, that's an interesting bug; while I'm not a developer, I'd suggest running the Oops text through ksymoops (with an appropriate System.map), and sending the decoded Oops to the list along with anything else relevant.

As a side node, it'd be nice if the network backend allowed for a pointopoint
topology, or the existing method.  Ie, I'd like it switchable.

Hack the script; there's nothing magical about the bridge setup, you can use traditional IP routing if you want. As pointed out in the documentation, the virtual network interfaces are simply like having NICs in between real systems, with a crossover cable interconnecting; you can do anything network-wise from there, the default assumption is simply that you'll want to start with bridging, because it's simple, and just like what most people are expecting.

--
Derrik Pates
dpates@xxxxxxxxxx


-------------------------------------------------------
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
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel