Xen users - Aug 2006 - xend, network-script and vif-script

Hi,
For a custom network setup, I want to modify the default
network-script and vif-scripts. So I made a copy of them and changed
the config in xend-config.sxp to use the copies which I want to
change.

Then I started adding my own features in the start and stop sections
and see what they do.
As they don''t do immediately what I want (oh, wonder?!  ),  I realize
they are hard to debug:
The problem I have here is that I don''t see where the output of these
scripts is written to for debugging and tracing purposes - no logfile
seems to contain stuff I echo from there, and no console.
Is there any configuration option to enable seeing more output from
these scripts? I cannot find any documentation for that, loglevel is
set to DEBUG in xend-config..sxp

Then I wondered if it''s right that the network-script is actuall never
called with stop as argument, while I would assume it will be called
when running xend stop.

I already started to read through the python code, because I didn''t
find any other information, but this will take some time until i
understand all the xend python code - maybe somebody has a hint?

Henning

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

Hi xen-developers,
I didn''t get any hint to this question from xen-users, but I am sure,
you know how I get to see the output (e.g. things printed with echo
for debuggin purposes) of the scripts I define as network-script and
vif-.script somewhere - do you?

Below a longer explanation, if you are interested.

---------- Forwarded message ----------
From: Henning Sprang <henning_sprang@gmx.de>
Date: Aug 9, 2006 10:45 PM
Subject: xend, network-script and vif-script
To: xen-users <xen-users@lists.xensource.com>


Hi,
For a custom network setup, I want to modify the default
network-script and vif-scripts. So I made a copy of them and changed
the config in xend-config.sxp to use the copies which I want to
change.

Then I started adding my own features in the start and stop sections
and see what they do.
As they don''t do immediately what I want (oh, wonder?!  ),  I realize
they are hard to debug:
The problem I have here is that I don''t see where the output of these
scripts is written to for debugging and tracing purposes - no logfile
seems to contain stuff I echo from there, and no console.
Is there any configuration option to enable seeing more output from
these scripts? I cannot find any documentation for that, loglevel is
set to DEBUG in xend-config..sxp

Then I wondered if it''s right that the network-script is actuall never
called with stop as argument, while I would assume it will be called
when running xend stop.

I already started to read through the python code, because I didn''t
find any other information, but this will take some time until i
understand all the xend python code - maybe somebody has a hint?

Henning

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

On 14/8/06 4:57 pm, "Henning Sprang" <henning_sprang@gmx.de>
wrote:
> Hi xen-developers,
> I didn''t get any hint to this question from xen-users, but I am
sure,
> you know how I get to see the output (e.g. things printed with echo
> for debuggin purposes) of the scripts I define as network-script and
> vif-.script somewhere - do you?
> 
> Below a longer explanation, if you are interested.
You should be able to echo to an explicit file. E.g.,
 echo "I am here" >/tmp/my-vif-script.log

 -- keir



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

On Mon, Aug 14, 2006 at 05:57:19PM +0200, Henning Sprang wrote:
> Hi xen-developers,
> I didn''t get any hint to this question from xen-users, but I am
sure,
> you know how I get to see the output (e.g. things printed with echo
> for debuggin purposes) of the scripts I define as network-script and
> vif-.script somewhere - do you?
It''s probably going into /var/log/xend-debug.log if you''re
using stderr.
Alternatively, you could use

. /etc/xen/scripts/logging.sh

log err "My message"

and it''ll end up in syslog.

HTH,

Ewan.



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

On 8/14/06, Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
wrote:
> [...]
> You should be able to echo to an explicit file. E.g.,
>  echo "I am here" >/tmp/my-vif-script.log
Thanks for the reply, actually, I already figrued that out, but it is
harder to work that way (more characters to write, start less instead
of just watch outpout - that gets annoying when you do it a hundred
times). I hoped there where some undocumented debug or verbose option
to xend and xm that would print that out.

(Why) is that output really just piped to /dev/null?

Henning

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