Re: [Xen-devel] network access disappears in master on /etc/init.d/xend start

[Brian Wolfe <brianw@xxxxxxxxxxxx>]

Disable ipv6 before you start up xend. As ian said in another email, the
xend scripts will reliably choke on the ipv6 addrs. 8-P

Dunno if the following Debian specific example will help any Debian fans
out there. The easiest thing to do is to disable IPv6 for now on
machines that use ifup/ifdown network script tools.

---- alternate network setup method - example only, alter to taste

WARNING: you can't recursively call ifup/ifdown from within ifup/ifdown.
8-( It will hang itself and then you are stuck unless you have serial or
local access. So any configuring withint the up, down, pre-up, post-down
lines MUST use the standard or other tools, never ifup/ifdown. I found
this out the hard way. :)

Add a xen-br0 interface to /etc/network/interfaces.
Do NOT add it to the "auto" list.

Next alter /etc/xen/scripts/network to do the following in the case
stanzas.

-- start
brctl addbr $br
brctl addif $br $dev
ifup xen-br0
ifconfig eth0 0.0.0.0.

-- stop
ifdown xen-br0, eth0
brctl delif $br $dev
ifconfig xen-br0 down
brctl delbr $br
ifup eth0

Note, this doesn't handle any remaining vifx.x interfaces that the
bridge may have still. 8-P Cleaning up any residual vifs and domains is
up to you. You should be stoping all but domain-0 prior to messing with
the network.


------

Personally, I'd rather see a separate network start/stop script for the
bridge setup from the init.d/xend script. That way you can restart xend
without bombing your network.

Alternatively, you could just make scripts/network return true and
use /etc/network/interfaces and pre-up, up, down, post-down keys in the
interfaces to setup the bridges prior to launching xen. 

That's my 0.02 cents. :) Hope it helps some people.

On Sun, 2004-11-21 at 14:37 +0100, Vitez Gabor wrote:
> On Sun, Nov 21, 2004 at 11:59:47AM +0000, Luke Kenneth Casson Leighton wrote:
> > hi,
> > 
> > i have made zero changes to the setup of the xend 2.0 code - everything
> > is as-is compiled from source off the sf.net site.
> > 
> > i ping 192.168.0.4 before starting /etc/init.d/xend, it hunky-dory.
> > 
> > i start xend: ping stops working as does everything else.
> 
> For debian/sarge+Xen I use the following setup:
> 
> I start xend from /etc/rcS.d/S38xend, so it's before S39ifupdown.
> 
> My /etc/network/interfaces looks like this:
> 
> ...
> auto xen-br0
> iface xen-br0 inet static
>         address WHATEVER
>         netmask WHATEVER
>         gateway WHATEVER
>         pre-up  /sbin/ifconfig eth0 up
> ....
> 
> 
> Hope that helps.
> 
>       Gabor
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: InterSystems CACHE
> FREE OODBMS DOWNLOAD - A multidimensional database that combines
> robust object and relational technologies, making it a perfect match
> for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/xen-devel
-- 



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel