Re: [Xen-devel] [OSSTEST PATCH 13/13] rump kernel tests: Run xenstore-ls demo

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Wed, 2014-07-16 at 11:15 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [OSSTEST PATCH 13/13] rump kernel tests: Run 
> xenstore-ls demo"):
> > On Tue, 2014-07-15 at 16:22 +0100, Ian Jackson wrote:
> > > We can use the newly-generalised ts-rumpuserxen-demo-setup to set up
> > > the config file etc. to run xenstore-ls from the xen.git build.
> ...
> > >              guests_rumpuserxenbuildjob=build-$rumparch-rumpuserxen   \
> > >              rump_builtimage=rumpuserxen:/usr/local/lib/xen/rump-kernel \
> > >              rump_cmdline=3                                           \> 
> > > > +            xenstorels_builtimage=:/usr/local/bin/xenstore           \
> > 
> > Really no distpart here? Doesn't that look in the main build job which
> > built the regular Xen not the rump one?
> 
> No, the job is that specified in guests_rumpuserxenbuildjob.
> 
> The distpart is <foo> in the runvar path_<foo>dist.  In this case we
> want the main output rather than the hypervisor (path_xendist, not
> built because we say `make tools') or kernel (path_kerndist, not built
> nowadays).  So the distpart is `'.

Ah yes, I was confusing this with ${thing}buildjob.

> > Assuming this is a path within the rump build target -- might it be wise
> > to override --prefix when building that to avoid surprising clashes?
> 
> I think it is easier to deal with this on the output end.  If you
> install the rump xen.git build's dist/install/ in your system's / you
> have only yourself to blame.

OK.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel