[Pkg-xen-devel] Problems starting xend.

[Nicklas Börjesson]

Hi all,
I know that this list isn't for usage and install level questions,  but the
people at  xen-users at lists.xensource.com had no idea of what could be the
problem and told me to get hold of a "debian-xen"-type list. Which yours
came closest to. :-)

My setup is a little bit strange, since i change the motherboard and
processor of the system from a K7 to an AMD 64 a couple of months ago. I was
a bit lazy, and i simply did not think that it would be a big problem.

Anyway, apt is configured to install 686 architecture packages, and changing
that to amd64 make it go ape and try to reinstall _everything_.

However, since all the xend-packages and images are of the correct amd64
.deb  flavour(--force-architecture) and doesn't use any platform specific
libraries(if one follows the dependencies), it should not matter....IMHO.
Right?

So, the problem is that it seems like python won't load the xc.so library,
even though there is a file at : /usr/lib/xen-3.0.3-1
/lib/python/xen/lowlevel/xc.so
Is the ../ in the path not understood by the system or what?

Here is the traceback of me trying to start xen:

Traceback (most recent call last):
  File "/usr/lib/xen-3.0.3-1/bin/xend", line 40, in ?
    from xen.xend.server import SrvDaemon
  File "/usr/lib/xen-3.0.3-1/bin/../lib/python/xen/xend/server/SrvDaemon.py",
line 17, in ?
    import xen.lowlevel.xc
ImportError: /usr/lib/xen-3.0.3-1/bin/../lib/python/xen/lowlevel/xc.so:
cannot open shared object file: No such file or directory


I am by no means a star of python programming, but as far as i understand of
its docs, the code should work. But it doesn't. I have tried moving around
the file and even modifying the python code.

At xen-users they said:
"That's a weird place for the library to be anyhow.  Normally it'd be
under /usr/lib/python/xen/lowlevel/xc.so.

IIRC, Debian has some extra smarts so that you can easily change between
multiple installed Xen versions.  Maybe the more complicated path your
system
uses is due to that."

In their view, I guess that makes it a packaging problem.

Warm regards
Nicklas Börjesson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20071011/0a9d5bda/attachment.htm