From: Min Lee <min.lee@gatech.edu>
To: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: xen-testing: xend doesn't start. undefined symbol: xc_cpupool_movedomain
Date: Tue, 13 Jul 2010 15:06:10 -0400 [thread overview]
Message-ID: <4C3CB922.4010100@gatech.edu> (raw)
In-Reply-To: <C86275B0.1A952%keir.fraser@eu.citrix.com>
Oh, I'll subscribe to user list.
thanks, Keir.
Min
On 7/13/2010 2:57 PM, Keir Fraser wrote:
> You have mismatching versions of variuous Xen libraries installed. In this
> case, the Xc.so extension package for Python is probably from xen-unstable,
> while your libxenctrl is probably from a stable branch. Hence the warning
> about an unresolved symbol.
>
> This doesn't belong on xen-devel by the way, it's a user question.
>
> -- Keir
>
> On 13/07/2010 19:31, "Min Lee"<min.lee@gatech.edu> wrote:
>
>> I tried current xen-testing with pvops-kernel, but xend doesn't start.
>> Here's the message below. any idea?
>> thanks for any help.
>> Min
>>
>> --
>>
>> root@ubuntu172:~# /etc/init.d/xend status
>> Traceback (most recent call last):
>> File "/usr/sbin/xend", line 36, in<module>
>> from xen.xend.server import SrvDaemon
>> File
>> "/usr/local/lib/python2.6/dist-packages/xen/xend/server/SrvDaemon.py", line
>> 20, in<module>
>> import xen.lowlevel.xc
>> ImportError: /usr/local/lib/python2.6/dist-packages/xen/lowlevel/xc.so:
>> undefined symbol: xc_cpupool_movedomain
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
>
>
prev parent reply other threads:[~2010-07-13 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 18:31 xen-testing: xend doesn't start. undefined symbol: xc_cpupool_movedomain Min Lee
2010-07-13 18:57 ` Keir Fraser
2010-07-13 19:06 ` Min Lee [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C3CB922.4010100@gatech.edu \
--to=min.lee@gatech.edu \
--cc=Xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).