Re: [Xen-users] Xen installation : Python C API mismatch

[Mark Williamson <mark.williamson@xxxxxxxxxxxx>]

On Thursday 17 July 2008, Antoine Benkemoun wrote:
> Thank you for your thorough answer !
>
> Indeed I am booting Debian with the Xen kernel perfectly. I don't know what
> you mean by XenLinux but I'm guessing it's what I am booting or something
> similar enough.

Sorry.

By XenLinux I mean the Xen-aware Linux you're booting on top of Xen.

> I agree that since it is the same version it shouldn't mess things up too
> much. I am compiling at the moment using the same tutorial (it had a
> compiling source page included). It's taking for ever even with a Quad Core
> Xen machine with 4GB of RAM...

If you're only installing the tools, as I suggested, you only actually need to 
do make tools; make install-tools, which should be much faster.  If you just 
do "make world" it'll build Xen and the XenLinux, which will take ages and 
you already have those.

> I'll keep you updated if this works or if I get a free trip to the
> datacentre :P

I hope you don't win that prize :-)

Cheers,
Mark

> Antoine
>
> On Thu, Jul 17, 2008 at 9:43 PM, Mark Williamson <
>
> mark.williamson@xxxxxxxxxxxx> wrote:
> > > Thank you for your quick answer.
> > >
> > > I installed the 3.1.0 binaries on a Lenny Sid installed. I followed the
> > > "Perfect Xen 3.0 install" tutorial to the letter.
> > >
> > > I have the possibility to install from sources but I am somewhat afraid
> >
> > to
> >
> > > do so... Can it crash the machine if installed ontop a previous install
> > > ? Basically, the machine not rebooting correctly wins me a trip to the
> > > datacentre and that's not fun :P
> >
> > Xen doesn't play very well with conflicting installs.  I guess if you're
> > installing the same version from source that you've just installed in
> > binaries it's not so likely to screw things up.  That said, most of the
> > conflicts are typically in userspace stuff, which shouldn't stop the
> > machine
> > actually booting.  I'd also not expect such conflicts to result in a
> > crash at
> > runtime, it just usually means Xend doesn't work properly.
> >
> > > Is it possible to uninstall a previous Xen install so it doesn't mess
> > > up everything ?
> >
> > Yes, if you can figure out which bits to remove.  I think there's a "make
> > uninstall" target in the source distribution that should do this
> > reasonably thoroughly for you; it's not included in the binary
> > distribution you currently have :-(
> >
> > *however* in your case, you have successfully installed Xen and XenLinux
> > by the sound of it and they're already booting - am I reading you right?
> >
> > If you get the source distribution for the same version of Xen and then
> > just
> > compile / install the userspace tools, that should do.  You probably
> > don't really need to build Xen / XenLinux lot again, or even reboot for
> > that matter.
> >
> > You might still need to remove the old userspace libraries to make Xend
> > work
> > right.  make uninstall should take them away but it might remove your Xen
> > / XenLinux too...  I'd suggest you manually look at what the Makefile
> > does to see which libraries / binaries to remove, then do it yourself. 
> > Does that sound reasonably doable to you?  Don't use make uninstall, just
> > use it for inspiration when uninstalling the userspace tools.  Then run
> > make tools-install to build and install a new version of the tools.
> >
> > You may need to install a few -dev packages to build successfully.
> >
> > Cheers,
> > Mark
> >
> > > On Thu, Jul 17, 2008 at 9:02 PM, Mark Williamson <
> > >
> > > mark.williamson@xxxxxxxxxxxx> wrote:
> > > > These errors typically happen when the Xen code was built against a
> > > > different
> > > > version of Python to the one that's available at runtime.  I've
> >
> > actually
> >
> > > > found these are often harmless but that's probably not an appropriate
> > > > risk to
> > > > take for a production machine.
> > > >
> > > > Where exactly did you get your install source for Xen from?  Could
> > > > you just build Xen yourself rather than using a pre-compiled version?
> > > >
> > > > Cheers,
> > > > Mark
> > > >
> > > > On Thursday 17 July 2008, Antoine Benkemoun wrote:
> > > > > Hello,
> > > > >
> > > > > I am trying to install Xen 3.1.0 on a Debian Sid. I have been able
> > > > > to do this type of installation correctly with it working perfectly
> >
> > before
> >
> > > > > but
> > > >
> > > > I
> > > >
> > > > > have to admit I can't get this one to work.
> > > > >
> > > > > Here are the error messages that I get at Xen startup :
> > > > >
> > > > > orangene1-hyp:~# /etc/init.d/xend start
> > > > > /usr/lib/python/xen/xend/server/SrvDaemon.py:20: RuntimeWarning:
> >
> > Python
> >
> > > > > C API version mismatch for module xen.lowlevel.xc: This Python has
> >
> > API
> >
> > > > > version 1013, module xen.lowlevel.xc has version 1012.
> > > > >   import xen.lowlevel.xc
> > > > > /usr/lib/python/xen/util/security.py:25: RuntimeWarning: Python C
> > > > > API version mismatch for module acm: This Python has API version
> > > > > 1013, module acm has version 1012.
> > > > >   from xen.lowlevel import acm
> > > > > /usr/lib/python/xen/xend/xenstore/xsutil.py:8: RuntimeWarning:
> > > > > Python
> >
> > C
> >
> > > > API
> > > >
> > > > > version mismatch for module xen.lowlevel.xs: This Python has API
> > > > > version 1013, module xen.lowlevel.xs has version 1012.
> > > > >   import xen.lowlevel.xs
> > > > > /usr/lib/python/xen/xend/XendBootloader.py:25: RuntimeWarning:
> > > > > Python
> >
> > C
> >
> > > > API
> > > >
> > > > > version mismatch for module ptsname: This Python has API version
> >
> > 1013,
> >
> > > > > module ptsname has version 1012.
> > > > >   from xen.lowlevel import ptsname
> > > > > /usr/lib/python/xen/xend/server/SrvDaemon.py:20: RuntimeWarning:
> >
> > Python
> >
> > > > > C API version mismatch for module xen.lowlevel.xc: This Python has
> >
> > API
> >
> > > > > version 1013, module xen.lowlevel.xc has version 1012.
> > > > >   import xen.lowlevel.xc
> > > > > /usr/lib/python/xen/util/security.py:25: RuntimeWarning: Python C
> > > > > API version mismatch for module acm: This Python has API version
> > > > > 1013, module acm has version 1012.
> > > > >   from xen.lowlevel import acm
> > > > > /usr/lib/python/xen/xend/xenstore/xsutil.py:8: RuntimeWarning:
> > > > > Python
> >
> > C
> >
> > > > API
> > > >
> > > > > version mismatch for module xen.lowlevel.xs: This Python has API
> > > > > version 1013, module xen.lowlevel.xs has version 1012.
> > > > >   import xen.lowlevel.xs
> > > > > /usr/lib/python/xen/xend/XendBootloader.py:25: RuntimeWarning:
> > > > > Python
> >
> > C
> >
> > > > API
> > > >
> > > > > version mismatch for module ptsname: This Python has API version
> >
> > 1013,
> >
> > > > > module ptsname has version 1012.
> > > > >   from xen.lowlevel import ptsname
> > > > >
> > > > > I have tried to install python from Sid and Lenny versions but none
> > > > > seem
> > > >
> > > > to
> > > >
> > > > > change any of this... I have no Python knowledge at all so I would
> >
> > like
> >
> > > > to
> > > >
> > > > > know if anybody would happen to have an idea concerning this
> > > > > problem.
> > > > >
> > > > > I will be happy to give you more info if there is something missing
> >
> > in
> >
> > > > this
> > > >
> > > > > post.
> > > > >
> > > > > Thank you in advance for your help,
> > > > >
> > > > > Antoine Benkemoun
> > > >
> > > > --
> > > > Push Me Pull You - Distributed SCM tool (
> > > > http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48
> > > >/pmpu/>
> >
> > <http://www.cl.cam.ac.uk/%7Emaw48/pmp
> >
> > > >u/> )
> >
> > --
> > Push Me Pull You - Distributed SCM tool (
> > http://www.cl.cam.ac.uk/~maw48/pmpu/<http://www.cl.cam.ac.uk/%7Emaw48/pmp
> >u/> )



-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

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