Something during xend startup needs iptables. The network script says antispoof is ''no'', so its not that. I''m not sure what requires iptables. The config file for v2.6 xen0 does not have the iptable modules needed on by default. This add those modules to the xen0 defconfig ===== linux-2.6.8.1-xen-sparse/arch/xen/configs/xen0_defconfig 1.19 vs edited ====--- 1.19/linux-2.6.8.1-xen-sparse/arch/xen/configs/xen0_defconfig Thu Sep 16 09:11:33 2004 +++ edited/linux-2.6.8.1-xen-sparse/arch/xen/configs/xen0_defconfig Fri Sep 17 13:59:29 2004 @@ -500,8 +500,8 @@ # CONFIG_IP_NF_MATCH_STATE is not set # CONFIG_IP_NF_MATCH_CONNTRACK is not set # CONFIG_IP_NF_MATCH_OWNER is not set -# CONFIG_IP_NF_MATCH_PHYSDEV is not set -# CONFIG_IP_NF_FILTER is not set +CONFIG_IP_NF_MATCH_PHYSDEV=m +CONFIG_IP_NF_FILTER=m # CONFIG_IP_NF_NAT is not set # CONFIG_IP_NF_MANGLE is not set # CONFIG_IP_NF_TARGET_LOG is not set ------------------------------------------------------- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
How does xend fail for you without these table configured? I run with the default configuration most of the time and have no problem starting xend. -- Keir> Something during xend startup needs iptables. The network script > says antispoof is ''no'', so its not that. I''m not sure what requires iptables. > The config file for v2.6 xen0 does not have the iptable modules needed > on by default. > > This add those modules to the xen0 defconfig > > > ===== linux-2.6.8.1-xen-sparse/arch/xen/configs/xen0_defconfig 1.19 vs edited ====> --- 1.19/linux-2.6.8.1-xen-sparse/arch/xen/configs/xen0_defconfig Thu Sep 16 09:11:33 2004 > +++ edited/linux-2.6.8.1-xen-sparse/arch/xen/configs/xen0_defconfig > Fri Sep 17 13:59:29 2004 > @@ -500,8 +500,8 @@ > # CONFIG_IP_NF_MATCH_STATE is not set > # CONFIG_IP_NF_MATCH_CONNTRACK is not set > # CONFIG_IP_NF_MATCH_OWNER is not set > -# CONFIG_IP_NF_MATCH_PHYSDEV is not set > -# CONFIG_IP_NF_FILTER is not set > +CONFIG_IP_NF_MATCH_PHYSDEV=m > +CONFIG_IP_NF_FILTER=m > # CONFIG_IP_NF_NAT is not set > # CONFIG_IP_NF_MANGLE is not set > # CONFIG_IP_NF_TARGET_LOG is not set > > > ------------------------------------------------------- > 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@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
" > 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
In any case, recent fixes should now mean that xend correctly daemonises itself with no external assistance. -- Keir> > " > 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Could you toss me your /etc/init.d/xend script that uses debian''s daemon-start-stop program? I should probably include this alteration in my .debs. :) On Mon, 2004-09-20 at 09:06, David Becker wrote:> " > 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@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
Hi, the new Xen2.0 beta, is it with 2.6 kernel? I remember that Ian talked about an esier install of the loopback install for a domain. Is this made automatic during an install today, or do we need to make the loopback files manually? Cheers Rune ------------------------------------------------------- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> Hi, the new Xen2.0 beta, is it with 2.6 kernel?Sparse trees for Linux 2.6 & 2.4 and NetBSD 2.0 are provided. make world now builds Linux 2.6 by default.> I remember that Ian talked about an esier install of the loopback > install for a domain. Is this made > automatic during an install today, or do we need to make the loopback > files manually?Right now, this is still manual. Cheers, Mark> > Cheers > Rune > > > > ------------------------------------------------------- > 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@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xen-devel------------------------------------------------------- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel