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] network root bridge problem

To: "James Harper" <JamesH@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] network root bridge problem
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Sun, 03 Oct 2004 15:30:05 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Sun, 03 Oct 2004 15:40:56 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Sun, 03 Oct 2004 22:49:18 +1000." <AEC6C66638C05B468B556EA548C1A77D3BE13F@trantor>
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
> In trying to get dom0 running diskless, i've come across the problem
> where for a short time there is no network connectivity and so iscsi is
> unreachable. What is the accepted workaround? I can think of the
> following:
> 
> . do it in initrd. I'd rather not put this sort of setup info in the
> initrd though.

You could allow your initrd to take configuration parameters from
the kernel command line (they're available as environment
variables in the linuxrc).

> . patch brctl to do it in one hit. Looks easy but is it safe? Someone
> mentioned that the whole exe may not be loaded at that point and so
> could fail to load the rest if it needs to.

If you're hacking brctl you could mlock the pages.

> . patch the kernel to support an 'add if to bridge + migrate address'
> ioctl. This is probably best and looks pretty easy via an extra
> parameter to the existing addif ioctl.

Rather than doing this, I'd be inclined to hack the bridge code
such that packets to a local IP are received rather than
bridged. The current situation is at best inconsistent, where if
a bridged interface has an IP address the host can still send
packets with that IP on the interface, but it just can't receive.
I'm not convinced that's the intended behaviour...

Ian



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel