From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Hohnbaum Subject: Re: [PATCH] xmtest network script check Date: Tue, 25 Jul 2006 07:37:23 -0700 Message-ID: <1153838243.8690.58.camel@localhost> References: <1153524384.8690.35.camel@localhost> <2b3842824f03c7a8ff173c1ee3187967@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <2b3842824f03c7a8ff173c1ee3187967@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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