From: Paul Larson <plars@linuxtestproject.org>
To: xen-devel <xen-devel@lists.sourceforge.net>
Subject: undefined symbol: xc_vmx_build
Date: Fri, 07 Jan 2005 17:03:28 -0600 [thread overview]
Message-ID: <1105139008.8950.55.camel@localhost.localdomain> (raw)
I'm guessing this is from the recently checked in vmx patches in
xeno-unstable?
# xend start
Traceback (most recent call last):
File "/usr/sbin/xend", line 33, in ?
from xen.xend.server import SrvDaemon
File "/lib/python/xen/xend/server/SrvDaemon.py", line 40, in ?
import channel
File "/lib/python/xen/xend/server/channel.py", line 3, in ?
import xen.lowlevel.xc; xc = xen.lowlevel.xc.new()
ImportError: /lib/python/xen/lowlevel/xc.so: undefined symbol:
xc_vmx_build
--
Paul Larson <plars@linuxtestproject.org>
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next reply other threads:[~2005-01-07 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 23:03 Paul Larson [this message]
2005-01-07 23:13 ` undefined symbol: xc_vmx_build Ian Pratt
[not found] <mailman.1105139060.23769@unix-os.sc.intel.com>
2005-01-07 23:59 ` adsharma
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=1105139008.8950.55.camel@localhost.localdomain \
--to=plars@linuxtestproject.org \
--cc=xen-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.