From: Gerd Knorr <kraxel@suse.de>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: help with bugs
Date: 05 Aug 2005 10:29:17 +0200 [thread overview]
Message-ID: <873bpon5wi.fsf@bytesex.org> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282959@liverpoolst.ad.cl.cam.ac.uk>
"Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk> writes:
> I'd like to appeal for some help tracking down a couple of bugs that
> we're struggling to reproduce:
>
> BUG62 eth0 -> veth0 in network script can loose network
I think the only sane way to fix this is to let the distribution tools
configure the network. Thats a bit harder to set up, but works more
reliable. Also the "if{up|down} <interface>" commands and the like
will work as usual then. Especially in case eth0 is configured via
dhcp the ip address copying is a bad idea. Unfortunaly it isn't very
good documented how all this works, especially the new veth0 thing.
IMHO it would be good if the network start script checks whenever any
bridges are already present in the system and don't touch the network
setup if that is the case. That should catch both network setup being
already done by the distro start scripts or by an earlier network
setup script run (when xend is restarted).
The setup I'm running looks like this (classic 2.x setup, no
veth0/vid0.0 used), in boot.local:
ip link set eth0 name hw-eth0
brctl addbr eth0
brctl addif eth0 hw-eth0
ip link set hw-eth0 up
ip link set eth0 up
Then let the network scripts setup eth0 (now a bridge) as usual and
tell xend that "eth0" is the bridge device it should add the vif
interfaces to.
cheers,
Gerd
--
panic("it works"); /* avoid being flooded with debug messages */
next prev parent reply other threads:[~2005-08-05 8:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 15:04 help with bugs Ian Pratt
2005-08-04 19:53 ` Anthony Liguori
2005-08-04 20:18 ` Sean Dague
2005-08-04 20:49 ` Nivedita Singhvi
2005-08-04 20:54 ` Jerone Young
2005-08-04 20:59 ` Nivedita Singhvi
2005-08-04 20:49 ` David F Barrera
2005-08-05 8:29 ` Gerd Knorr [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-04 21:02 Ian Pratt
2005-08-04 21:29 ` David F Barrera
2005-08-04 21:55 ` Paul Larson
2005-08-05 3:10 ` David F Barrera
2005-08-04 21:48 Ian Pratt
2005-08-04 22:21 ` Sean Dague
2005-08-05 9:12 Ian Pratt
2005-08-05 13:20 ` Gerd Knorr
2005-08-10 18:38 ` Nivedita Singhvi
2005-08-05 14:22 Ian Pratt
2005-08-10 18:39 Ian Pratt
2005-08-10 19:00 ` Nivedita Singhvi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873bpon5wi.fsf@bytesex.org \
--to=kraxel@suse.de \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.