This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: is the xen toolstack backwards compatible ?

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: is the xen toolstack backwards compatible ?
From: Christoph Egger <Christoph.Egger@xxxxxxx>
Date: Wed, 9 Dec 2009 11:06:58 +0100
Cc: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 09 Dec 2009 02:08:13 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C74500A6.3EE2%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C74500A6.3EE2%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.10
On Wednesday 09 December 2009 08:22:14 Keir Fraser wrote:
> On 09/12/2009 00:23, "Sander Eikelenboom" <linux@xxxxxxxxxxxxxx> wrote:
> > So if it was no coincidence but desirable, at the moment xend and xentop
> > from unstable don't seem to work on 3.4.2 hypervisor anymore.
> There's no compatibility guarantee across different major Xen releases. But
> Christoph Egger did a lot of work to allow multiple toolstacks to be
> installed side by side. I think you should just need to specify a
> PREFIX=/path/to value when building the tools. Is that right, Christoph?

Yes, this is right.
*Before* you start xend, you need to set two environment variables

Here is an example for PREFIX="/usr/local" and compiled with python 2.5:

export LD_LIBRARY_PATH="/usr/local/lib"
export PYTHONPATH="/usr/local/lib/python2.5/site-packages"

If these are not set correct, python tells you it can't find its modules or
the dynamic linker tells you it can't find the shared libs built from 

You should use the same python version you compiled with.
If you are on a machine where 'python' does not exist as a symbolic link to
the installed python version (like me on NetBSD) you need the attached patch
or all python programs installed with "INSTALL_PYTHON_PROG"
end up with '#!' in the first line instead of '#!/path/to/python2.5'
which is stupid.

I already submitted attached patch earlier but Ian Jackson objected it because
he wants a way to have tools working with a different python version than it
has been compiled with. This sounds obscure to me when looking at the path 
python modules get installed to.

Keir: Please take attached patch. This is better than the current situation
regardless Ian likes it or not. In the latter case taking the patch should 
motivate him to come up with a patch finally. :)

Signed-off-by: Christoph Egger <Christoph.Egger@xxxxxxx>

Attachment: xen_python.diff
Description: Text Data

Xen-devel mailing list