From: David F Barrera <dfbp@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>, ewan@xensource.com
Subject: Re: [Fwd: x86_64 - ImportError: /usr/lib64/python2.4/xen/lowlevel/xc.so: undefined symbol:,xc_evtchn_status]
Date: Mon, 21 Aug 2006 11:00:47 -0500 [thread overview]
Message-ID: <44E9D8AF.6070006@us.ibm.com> (raw)
In-Reply-To: <C10B9271.110C%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser wrote:
>
> On 18/8/06 3:45 pm, "David F Barrera" <dfbp@us.ibm.com> wrote:
>
>
>> Ewan,
>>
>> What about this issue? Is there a patch for this as well? I am still
>> seeing this error with the latest changeset:
>>
>
> There's a lot of stuff stuck in the staging tree right now. We just fixed a
> bug which should result in everything being pushed to the public tree in a
> couple of hours.
>
> -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
Still unable to start xend on my SLES 10 x86_64 box, using CS 11212
dated Aug 21.
# xend start
Traceback (most recent call last):
File "/usr/sbin/xend", line 49, in ?
from xen.xend.server import SrvDaemon
File "//usr/lib64/python/xen/xend/server/SrvDaemon.py", line 17, in ?
import xen.lowlevel.xc
ImportError: /usr/lib64/python2.4/xen/lowlevel/xc.so: undefined symbol:
xc_evtchn_status
# hg tip
changeset: 11212:58ed222274f2
tag: tip
user: kfraser@localhost.localdomain
date: Mon Aug 21 03:01:53 2006 +0100
summary: [XEN] Remove unnecessary printk from invalid opcode debug
output.
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
prev parent reply other threads:[~2006-08-21 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 14:45 [Fwd: x86_64 - ImportError: /usr/lib64/python2.4/xen/lowlevel/xc.so: undefined symbol:,xc_evtchn_status] David F Barrera
2006-08-18 14:51 ` Keir Fraser
2006-08-21 16:00 ` David F Barrera [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=44E9D8AF.6070006@us.ibm.com \
--to=dfbp@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=ewan@xensource.com \
--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 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.