| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
RE: [Xen-users] RE: xend stop doesn't call network-script stop
Hello All!
For those of you who want to know, how that story ended: I removed all
those laborious written network scripts, replaced it by
(network-script 'network-bridge-dummy')
in the xend-config.sxp (which does simply nothing) and configured my two
bridges over bonding with the redhat scripts.
Advantages:
+ iptables is the same always
+ xend can be stopped and started at will
+ 'service network restart' ist working
+ bond0 is not promiscous (if MACADDR=xy is specified in both the eth0
and eth1)
Oh, yes: Pls use >2.6.16 for that otherwise you will run into that
bridging problem having the own MAC on the wrong side. See
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=c
ommit;h=8f903c708fcc2b579ebf16542bf6109bad593a1d
br
Walter
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Schober
Walter
Sent: Tuesday, May 15, 2007 4:08 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] RE: xend stop doesn't call network-script stop
Hello Daniel!
I agree on that point below! I'd like to leave networing to the distro,
but the thing is, that the vif0.X - vethX links do not work anymore w/o
xend running, isn't it?
And I read in some Howto that I should use vethX even in Dom0 because of
priorization of traffic and penalties to DomUs, if Dom0 has IP attached
to the xenbr directly.
Anyway, I can deal with it - it's just impossible to restart xend during
operation then, because those redhat scripts together with bonding do
work only on clean start (ifup on bond device, where slaves already
attached .... brrrr).
br
Walter
-----Original Message-----
From: Daniel P. Berrange [mailto:berrange@xxxxxxxxxx]
Sent: Tuesday, May 15, 2007 3:59 PM
To: Schober Walter
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] RE: xend stop doesn't call network-script stop
>Having 'service xend start' futz around with networking is
(reasonably)
>safe because at the time you boot most apps[1] won't be using
networking
>so their connectivity won't be disrupted. If you call 'service xend
start'
>multiple times the subsequent times will be no-op. If 'service xend
stop'
>were to call network-bridge to shutdown networking then this would
cause
>serious disruption to any apps using networking at the time.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home