Xen users - May 2007 - xend stop doesn''t call network-script stop

"service xend start" calls the script configured in xend-config.sxp
with
parameter "start" perfectly. The network get''s setup and is
working,
too.
But on stopping xend with "service xend stop" that script
doesn''t get
called. 
Doing it manually works great as well. Even set -x in the network script
doesn''t give me any output on the /var/log/xend-debug.log on
"service
xend stop".
 
What have I missed here?
 
br
Walter


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Attached my network-bridge-bonding script, if helpful for someone. 
 
Is it normal, that 
root      5450     1  0 03:12 ?        00:00:00 python /usr/sbin/xend
start
root      5453  5450  0 03:12 ?        00:00:00 python /usr/sbin/xend
start
stays running that way?
 
Any other hint, why ''service xend stop'' doens''t call
the script?
 
I''m about to believe, that this isn''t really interesting thus
no one
really cares about to get the "stop" working, too.
My scripts work perfectly, if called in the shell.
 
br
Walter
----
Centos 5, Xen 3.0.3
 


________________________________

From: Schober Walter 
Sent: Sunday, May 06, 2007 12:26 PM
To: xen-users@lists.xensource.com
Subject: xend stop doesn''t call network-script stop


"service xend start" calls the script configured in xend-config.sxp
with
parameter "start" perfectly. The network get''s setup and is
working,
too.
But on stopping xend with "service xend stop" that script
doesn''t get
called. 
Doing it manually works great as well. Even set -x in the network script
doesn''t give me any output on the /var/log/xend-debug.log on
"service
xend stop".
 
What have I missed here?
 
br
Walter




_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Tue, May 15, 2007 at 03:51:03PM +0200, Schober Walter
wrote:
> Attached my network-bridge-bonding script, if helpful for someone. 
>  
> Is it normal, that 
> root      5450     1  0 03:12 ?        00:00:00 python /usr/sbin/xend
> start
> root      5453  5450  0 03:12 ?        00:00:00 python /usr/sbin/xend
> start
> stays running that way?
Yes, the parent process is a ''guardian angel'' so to speak,
while the
second is the actual XenD server. The former will restart the latter
if it crashes. 
> Any other hint, why ''service xend stop'' doens''t
call the script?
>  
> I''m about to believe, that this isn''t really interesting
thus no one
> really cares about to get the "stop" working, too.
> My scripts work perfectly, if called in the shell.
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.

To be honest, XenD has no business touching networking what-so-ever.
Even at boot time, this will totally hose your system if you are booting
of iSCSI or NFS root. Longer term, I''d like to see Xend''s
network-script
going  away completely & with the setup  being left to the regular distro
provided networking scripts which are already capable of setting up far more
complex & interesting configurations in a safer manner.

Regards,
Dan.

[1] iSCSI / NFS boot being the counter-examples
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

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@redhat.com] 
Sent: Tuesday, May 15, 2007 3:59 PM
To: Schober Walter
Cc: xen-users@lists.xensource.com
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@lists.xensource.com
http://lists.xensource.com/xen-users

On Tue, May 15, 2007 at 04:07:59PM +0200, Schober Walter
wrote:
> 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?a
Yes, that''s the core blocking problem at the moment. Work is being
undertaken to remove need for the vethX stuff in future Xen release.
> 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).
You could put some logic in the ''start'' method so that it does
nothing if
it detects the bonding stuff is already setup.

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

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@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Schober
Walter
Sent: Tuesday, May 15, 2007 4:08 PM
To: xen-users@lists.xensource.com
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@redhat.com] 
Sent: Tuesday, May 15, 2007 3:59 PM
To: Schober Walter
Cc: xen-users@lists.xensource.com
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@lists.xensource.com
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users