Fallback behaviour of the network startup script is now same as it
always was: IP addresses of eth0 are transferred to the bridge device
but not deleted from eth0. This is needed for the 2.0-series tools,
which by default look only at eth0 to determine IP parameters for domU.
Signed-off-by: Keir Fraser <keir@xensource.com>
network:
Handle xend restart -- don't take down the network setup and don't
initialize it if it looks already initialized.
Signed-off-by: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Many files:
Make interface to network/block scripts consistent:
- output on stdout is returned to the script caller
- output on stderr is logged at the error level, messages with a '-' prefix
are logged at the debug level and messages with a '*' prefix are logged
at the info level.
Signed-off-by: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
With ipv6, every network interface always has a link local
address. This fools the network script into thinking that
xen-br0 already has a network address, and it refuses to
transfer over eth0's IP address to xen-br0.
By grepping for 'inet ' instead of just 'inet', the network
script is no longer fooled and does the right thing. This
patch makes Xen networking work again on my Fedora system.
Signed-off-by: Rik van Riel <riel@redhat.com>
Signed-off-by: ian.pratt@cl.cam.ac.uk
Don't set bridge hello time (specifically not to 0) since Linux 2.6 bridge
code doesn't deal well with sethello == 0 (domain doesn't block and thus
consumes cycles constantly).
kaf24@firebug.cl.cam.ac.uk
cl349@firebug.cl.cam.ac.uk
iap10@labyrinth.cl.cam.ac.uk
mjw@wray-m-3.hpl.hp.com
cl349@freefall.cl.cam.ac.uk