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

Thank you very much for your help guys !

I ended just reinstalling ontop of a clean Debian Etch Stable. Worked perfectly fine using the binary and seems to be running stable.

Antoine

On Fri, Jul 18, 2008 at 3:09 PM, Alexander Hoßdorf <xen-users@xxxxxxxxxxx> wrote:

may this perhaps be a bug?
I found this:
http://markmail.org/message/mujwmt5tstg34mh6

I'm not familiar with overflow checks.
But you might try this out, I think you've nothing to lose ;-)
Backup your xc_core.c before editing.

Hope this helps...

Cheers,
Alex

Antoine Benkemoun schrieb:

Thank you for taking the time to re-explain everything.

You have understood my situation right.

I have applied your script. Gotten the sources. But make install-tools seems to start correctly but fails since /etc/init.d/xend doesn't appear and errors appear.

Here is the detail :

orangene2-hyp:~/xen-3.1.0-src# make install-tools
make -C tools install
make[1]: Entering directory `/root/xen-3.1.0-src/tools'
make -C check
make[2]: Entering directory `/root/xen-3.1.0-src/tools/check'
XENFB_TOOLS=n ./chk build
Xen CHECK-BUILD Fri Jul 18 09:07:51 CEST 2008
Checking check_crypto_lib: OK
Checking check_libvncserver: unused, OK
Checking check_openssl_devel: OK
Checking check_python: OK
Checking check_python_devel: OK
Checking check_sdl: unused, OK
Checking check_x11_devel: OK
Checking check_xgettext: OK
Checking check_zlib_devel: OK
Checking check_zlib_lib: OK
make[2]: Leaving directory `/root/xen-3.1.0-src/tools/check'
make[2]: Entering directory `/root/xen-3.1.0-src/tools/libxc'
mkdir -p xen
( cd xen && ln -sf ../../../xen/include/public/*.h . )
mkdir -p xen/hvm
( cd xen/hvm && ln -sf ../../../../xen/include/public/hvm/*.h . )
mkdir -p xen/io
( cd xen/io && ln -sf ../../../../xen/include/public/io/*.h . )
mkdir -p xen/arch-x86
( cd xen/arch-x86 && ln -sf ../../../../xen/include/public/arch-x86/*.h . )
mkdir -p xen/foreign
( cd xen/foreign && ln -sf ../../../../xen/include/public/foreign/Makefile . )
( cd xen/foreign && ln -sf ../../../../xen/include/public/foreign/reference.size . )
( cd xen/foreign && ln -sf ../../../../xen/include/public/foreign/*.py . )
make -C xen/foreign
make[3]: Entering directory `/root/xen-3.1.0-src/tools/libxc/xen/foreign'
./checker > x86_32.size
diff -u reference.size x86_32.size
make[3]: Leaving directory `/root/xen-3.1.0-src/tools/libxc/xen/foreign'
mkdir -p xen/linux
( cd xen/linux && \
ln -sf ../../../../linux-2.6-xen-sparse/include/xen/public/*.h . )
( cd xen && rm -f sys && ln -sf linux sys )
make libxenctrl.a libxenctrl.so libxenctrl.so.3.0 libxenctrl.so.3.0.0 libxenguest.a libxenguest.so libxenguest.so.3.0 libxenguest.so.3.0.0
make[3]: Entering directory `/root/xen-3.1.0-src/tools/libxc'
gcc -O2 -fomit-frame-pointer -m32 -march=i686 -DNDEBUG -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -D_GNU_SOURCE -Werror -Wmissing-prototypes -fno-strict-aliasing -I. -I../xenstore -Wp,-MD,.xc_core.o.d -c -o xc_core.o xc_core.c
cc1: warnings being treated as errors
xc_core.c: In function 'xc_core_shdr_get':
xc_core.c:195: error: assuming signed overflow does not occur when assuming that (X + c) < X is always false
make[3]: *** [xc_core.o] Error 1
make[3]: Leaving directory `/root/xen-3.1.0-src/tools/libxc'
make[2]: *** [build] Error 2
make[2]: Leaving directory `/root/xen-3.1.0-src/tools/libxc'
make[1]: *** [install] Error 2
make[1]: Leaving directory `/root/xen-3.1.0-src/tools'
make: *** [install-tools] Error 2

Antoine

On Thu, Jul 17, 2008 at 10:53 PM, Mark Williamson <mark.williamson@xxxxxxxxxxxx <mailto:mark.williamson@xxxxxxxxxxxx>> wrote:

On Thursday 17 July 2008, Antoine Benkemoun wrote:
> I have to admit I am a bit lost here. Concerning userspace
tools, I don't
> really know what you are talking about.

OK, sorry, lets step back a bit.

If you want your host to *boot* you need the Xen hypervisor
(xen.gz) and
XenLinux (vmlinuz-xen or somesuch) and an initrd.

I understood from your previous e-mails that you've installed
these, set up
menu.lst to boot them and successfully booted into them. Is that
right?
This means you've got a running dom0.

>From this system, you're then trying to run xend and it's giving
loads of
errors about Python C API mismatches. I'm I correct so far?

> Also, the command lines you have given me will remove Xen. After
that's
> done, do I just reinstall using the binaries or do I do
something else ?

A Xen-based system has three main components: the Xen hypervisor,
the dom0
Linux kernel and the userspace tools. You seem to have the first
two working
OK, I think?

The problem you're seeing when starting Xend is strictly a
userspace tools
issue. xend is just a daemon that's written in Python and C which
issues
control hypercalls to Xen to tell it what to do. To fix this
issue you only
need to fix these tools.

The command lines I gave you will remove all the *userspace* parts
of Xen but
should (if I've editted them right) leave the Xen hypervisor and
the XenLinux
kernel you're using in place. This should leave the machine still
bootable
(assuming I'm correct in thinking you've successfully booted
Xen/XenLinux
already).

Using a source tree of the same version of Xen, "make
install-tools" should
replace the stuff we just removed with a custom-built copy,
allowing you to
start Xend without errors. That's the plan. You shouldn't even
need to
reboot. You should still be able to do this on the box you didn't
reboot...

> I am starting to think that this is going to be too complex to
fix. I think
> the big error that I made is trying to install it on a Lenny
Sid. I don't
> remember that ever working for me... I think just installing it
on a Stable
> Etch should do the trick without having to bother to spend hours
patching
> this to achieve mediocre stability.
>
> Does anyone happen to have any feedback on install Xen on a
Debian Sid
> Lenny or Sid Etch ? I don't recall that ever working on previous
occasions.

I think that Etch, at least, has reasonably recent Xen packages.
How about
just using the Debian-provided packages, at least to start with?
XenSource
don't guarantee to keep updating their kernels with security / bug
fixes so
you might find that the Debian kernels are more up-to-date.

Cheers,
Mark

> Antoine
>
> On Thu, Jul 17, 2008 at 10:32 PM, Mark Williamson <
>
> mark.williamson@xxxxxxxxxxxx
<mailto:mark.williamson@xxxxxxxxxxxx>> wrote:
> > On Thursday 17 July 2008, you wrote:
> > > I just did make install-tools and it didn't change anything.
I don't
> > > know if I was supposed to do something else for it to take
action.
> >
> > Bad luck with getting the free trip, I was hoping to avoid
that for you.
> >
> > :-(
> >
> > make install-tools should work, it's only a userspace problem
you have.
> > Did
> > you try to uninstall the existing userspace tools first as I
suggested?
> > Reinstalling Xen / XenLinux will *definitely* not help with
Python <-> C
> > API
> > problems.
> >
> > I went and poked in the Makefile for you and found that "make
uninstall"
> > runs
> > the following (I've removed the lines that delete the
hypervisor and the
> > XenLinux kernel stuff, since you want to keep those).
> >
> > You should substitute appropriate values for the environment
variables.
> > $(D)
> > should be set to the empty string, LIBDIR is probably
/usr/lib. Please
> > double check the following commands for sanity as you always
should
> > before rm -rf. Don't trust me too much :-)
> >
> > rm -rf $(D)/etc/init.d/xend*
> > rm -rf $(D)/etc/hotplug/xen-backend.agent
> > rm -f $(D)/etc/udev/rules.d/xen-backend.rules
> > rm -f $(D)/etc/udev/xen-backend.rules
> > rm -f $(D)/etc/sysconfig/xendomains
> > rm -rf $(D)/var/run/xen* $(D)/var/lib/xen*
> > rm -rf $(D)/usr/bin/xen* $(D)/usr/bin/lomount
> > rm -rf $(D)/usr/bin/cpuperf-perfcntr
$(D)/usr/bin/cpuperf-xen
> > rm -rf $(D)/usr/bin/xc_shadow
> > rm -rf $(D)/usr/bin/pygrub
> > rm -rf $(D)/usr/bin/setsize $(D)/usr/bin/tbctl
> > rm -rf $(D)/usr/bin/xsls
> > rm -rf $(D)/usr/include/xenctrl.h
$(D)/usr/include/xenguest.h
> > rm -rf $(D)/usr/include/xs_lib.h $(D)/usr/include/xs.h
> > rm -rf $(D)/usr/include/xen
> > rm -rf $(D)$(LIBDIR)/libxenctrl* $(D)$(LIBDIR)/libxenguest*
> > rm -rf $(D)$(LIBDIR)/libxenstore*
> > rm -rf $(D)$(LIBDIR)/python/xen $(D)$(LIBDIR)/python/grub
> > rm -rf $(D)$(LIBDIR)/xen/
> > rm -rf $(D)/usr/lib/xen/
> > rm -rf $(D)/usr/local/sbin/setmask $(D)/usr/local/sbin/xen*
> > rm -rf $(D)/usr/sbin/xen* $(D)/usr/sbin/netfix
$(D)/usr/sbin/xm
> > rm -rf $(D)/usr/share/doc/xen
> > rm -rf $(D)/usr/share/xen
> > rm -rf $(D)/usr/share/man/man1/xen*
> > rm -rf $(D)/usr/share/man/man8/xen*
> >
> > Cheers,
> > Mark
> >
> > > Antoine
> > >
> > > On Thu, Jul 17, 2008 at 10:22 PM, Antoine Benkemoun <
> > >
> > > antoine.benkemoun@xxxxxxxxx
<mailto:antoine.benkemoun@xxxxxxxxx>> wrote:
> > > > Critical failure... machine doesn't boot anymore. I win
the free trip
> > > > !
> > > >
> > > > I am trying to do just make install-tools on the second
machine just
> > > > to see if it will change something.
> > > >
> > > > Antoine
> > > >
> > > >
> > > > On Thu, Jul 17, 2008 at 10:01 PM, Antoine Benkemoun <
> > > >
> > > > antoine.benkemoun@xxxxxxxxx
<mailto:antoine.benkemoun@xxxxxxxxx>> wrote:
> > > >> Ah sorry I didn't read your email correctly.
> > > >>
> > > >> I will do that afterwards might just as well finish since
it's been
> > > >> running for quite a while...
> > > >>
> > > >> Won't be forgetting to do the initrd, thank you for reminder.
> > > >> Already got trapped previously but the PC was right next
to me so it
> > > >> wasn't so bad.
> > > >>
> > > >> Thanks !
> > > >>
> > > >> Antoine
> > > >>
> > > >>
> > > >> On Thu, Jul 17, 2008 at 9:55 PM, Mark Williamson <
> > > >>
> > > >> mark.williamson@xxxxxxxxxxxx
<mailto:mark.williamson@xxxxxxxxxxxx>> wrote:
> > > >>> 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
<mailto: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
<mailto: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.u

> > > >>> > > > >k/%7Emaw48/pmpu/>
> >
> > <http://www.cl.cam.ac.uk/%7
> >
> > > >>> > > > >Emaw48/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/pmpu/><http://www.cl.cam.ac.uk/%7
> > > >>> > >Emaw48/pmpu/>
> >

> > <http://www.cl.cam.ac.uk/%7Emaw
> >
> > > >>> > >48/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/pmpu/><http://www.cl.cam.ac.uk/%7Emaw

> > > >>>48/pmpu/>
> >
> > <http://www.cl.cam.ac.uk/%7Emaw48/p
> >
> > > >>>mpu/> )
> > > >>
> > > >> --
> > > >> Antoine Benkemoun
> > > >> Tel : 03.51.53.57.00
> > > >> Port : 06.32.88.59.35
> > > >
> > > > --
> > > > Antoine Benkemoun
> > > > Tel : 03.51.53.57.00
> > > > Port : 06.32.88.59.35
> >
> > --
> > 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/pmpu/>)

--
Antoine Benkemoun
Tel : 03.51.53.57.00
Port : 06.32.88.59.35
------------------------------------------------------------------------

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

--
Antoine Benkemoun
Tel : 03.51.53.57.00
Port : 06.32.88.59.35

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

WARNING - OLD ARCHIVES

xen-users

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