From: Michael Hohnbaum <hohnbaum@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] xmtest network script check
Date: Tue, 25 Jul 2006 07:37:23 -0700 [thread overview]
Message-ID: <1153838243.8690.58.camel@localhost> (raw)
In-Reply-To: <2b3842824f03c7a8ff173c1ee3187967@cl.cam.ac.uk>
On Tue, 2006-07-25 at 11:35 +0100, Keir Fraser wrote:
> On 22 Jul 2006, at 00:26, Michael Hohnbaum wrote:
>
> > The network script check in xmtest needs to look for "network" as
> > a valid script name, and if found set netenv to bridge. This patch
> > does that and allows xmtest to run on a normal install.
>
> I don't believe we have an out-of-the box script called 'network'. So
> where does it come from?
Excellent question. Looking at this system, it appears the
'network' script is called from /etc/xen/xend-config.sxp. Turns
out both the 'network' script and the xend-config.sxp file both
were created on this machine in April 2005. The machine has not
been used for quite a while (at least since sometime last year),
so these files are stale from a long past install.
Last week I downloaded xen, make world, make install,
then ran xm-test and stumbled across this problem. Apparently,
the install world did not replace/update xend-config.sxp. So,
ignore the patch. While it solved my problem, it is not relevant
to the larger Xen community. If anything needs to be done, it is
fixing the install process to update xend-config.sxp.
Michael
>
> -- Keir
>
--
Michael Hohnbaum 503-578-5486
hohnbaum@us.ibm.com T/L 775-5486
prev parent reply other threads:[~2006-07-25 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 23:26 [PATCH] xmtest network script check Michael Hohnbaum
2006-07-25 10:35 ` Keir Fraser
2006-07-25 14:37 ` Michael Hohnbaum [this message]
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=1153838243.8690.58.camel@localhost \
--to=hohnbaum@us.ibm.com \
--cc=Keir.Fraser@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.