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] nfsroot and brige

To: "Adam Sulmicki" <adam@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] nfsroot and brige
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Wed, 12 Jan 2005 21:08:15 -0000
Delivery-date: Wed, 12 Jan 2005 21:09:37 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
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
Thread-index: AcT46QC3XXhRDAbTRBqr7dxYqZAVNgAAIaPQ
Thread-topic: [Xen-devel] nfsroot and brige
> hello,
>       it seems like a catch-22 to me. I boot xen0 with nfsroot,
>       and then try to setup bridge stuff. something like this
> 
> /sbin/brctl addbr xen-br0
> /sbin/brctl addif xen-br0 eth0
> /sbin/ifconfig xen-br0 10.0.10.103 netmask 255.255.255.0 up
> /sbin/ifconfig eth0 0.0.0.0 promisc up
> 
>       however, once I start it running it crashes down with error
>       that nfs server is not available.
> 
>       does it mean that I must use initramfs to configure bridge
>       first, or is there some other way?

It really bugs me that there's no atomic way to configure a bridge and
transfer an IP address already active on another interface to it. I'm
not 100% convinced that the current behaviour is actually what the
bridge code author's intend: a the host can still transmit packet's with
an IP associated with an eth interface that is part of a bridge, it just
can't receive packets on that IP. I'd certainly appreciate it if someone
could ask the question on the bridge mailing list...

The workarounds for using nfsroot in dom0 at the moment are: a) use a
ramfs to configure the bridge; b) use a routed rather than bridged
setup.

I'm actually going off the whole idea of bridging rather than routeing
as the default...

Ian


-------------------------------------------------------
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

<Prev in Thread] Current Thread [Next in Thread>