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] v2.6 xen0 defconfig

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] v2.6 xen0 defconfig
From: David Becker <becker@xxxxxxxxxxx>
Date: Mon, 20 Sep 2004 10:06:00 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 20 Sep 2004 15:08:28 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <E1C8QYg-0001lb-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>
References: <20040917181219.GR921@xxxxxxxxxxx> <E1C8QYg-0001lb-00@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6+20040523i
" > Something during xend startup needs iptables.  The network script

" How does xend fail for you without these table configured? I run with

The domain had no network access, because the vif wasn't being added to
the bridge correctly.   Turns out the problem was that xend wouldn't run
the network script successfully when run outside a normal foreground
process context.  The config options were not the real problem (unlike
what I had posted last time). oops


After further review, I think I know what happened.   When I started
xend remotely,   xenU domain's could not send or recv any network packets.
While trying to figure why networking failed,  I had run
the xen/scripts/network file by hand.  The script has anit-spoof on by
default, which is what requires the ipt_physdev and iptable_filter module.
After I ran network by hand, the remote tool I used (a customized gexec)
could start xend OK.  I mistakenly concluded the iptables modules were
required.

Later I discovered the tool's deamon-ize option didn't play well with
xend, but Debian's start-stop-daemon can daemonize xend just fine.

So start-stop-daemon solves my original problem, and the extra config
options I posted are just needed when running xen/scripts/network with
anti-spoof turned on. 


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

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