WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: Christoph Egger <Christoph.Egger@xxxxxxx>
Subject: [Xen-devel] Re: is the xen toolstack backwards compatible ?
From: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
Date: Wed, 9 Dec 2009 12:25:40 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Wed, 09 Dec 2009 03:26:29 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200912091106.58517.Christoph.Egger@xxxxxxx>
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>
Organization: Eikelenboom IT services
References: <C74500A6.3EE2%keir.fraser@xxxxxxxxxxxxx> <200912091106.58517.Christoph.Egger@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hmmm so i could make  the paths:

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


And let a startup script make symlinks to the right tools for the hypervisor 
version that is booted (and perhaps config files), then the only place to worry 
about hypervisor and kernel version is grub.

But i think it's perhaps not worth the trouble and a bit ugly to make that 
general, so just drop the idea :-)

--

Sander


Wednesday, December 9, 2009, 11:06:58 AM, you wrote:

> 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
> LD_LIBRARY_PATH and PYTHONPATH.

> 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 
> tools/libxc.

> 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. :)

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



-- 
Best regards,
 Sander                            mailto:linux@xxxxxxxxxxxxxx


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