xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Michal Novotny <minovotn@redhat.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: Xen-unstable save error
Date: Mon, 21 Jun 2010 14:08:48 +0100	[thread overview]
Message-ID: <C84522F0.180EE%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4C1F61C5.90600@redhat.com>

On 21/06/2010 13:57, "Michal Novotny" <minovotn@redhat.com> wrote:

> Well, those are objdumps:
> 
> $ objdump -x /xen-unstable.hg/tools/xcutils/xc_save | grep xs_sus
> 0000000000000000       F *UND*  00000000000000ad
> xs_suspend_evtchn_port
> $ objdump -x /usr/lib64/xen/bin/xc_save | grep xs_suspend
> 0000000000000000       F *UND*  00000000000000ad
> xs_suspend_evtchn_port
> $ ls -al /usr/lib64/libxenctrl.so
> lrwxrwxrwx 1 root root 17 Jun 21 13:52 /usr/lib64/libxenctrl.so ->
> libxenctrl.so.4.0
> 
> I was having some libxenctrl* files at /lib64 so I removed them in order
> to make linked link those from /usr/lib64 so it did. However, the error
> now is:

Well what was the above supposed to achieve? xs_suspend_evtchn_port is
provided by libxenstore. It's that library which is getting mis-linked.
Moving the xc_save binary itself, and/or libxenctrl, isn't going to change
that. Go use ldd to find what libxenstore is being linked against; work out
why it's the wrong one; put the right one in its place.

 -- Keir

  reply	other threads:[~2010-06-21 13:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-21 11:15 Xen-unstable save error Michal Novotny
2010-06-21 12:05 ` Keir Fraser
2010-06-21 12:38   ` Michal Novotny
2010-06-21 12:44     ` Keir Fraser
2010-06-21 12:47       ` Michal Novotny
2010-06-21 12:56         ` Keir Fraser
2010-06-21 13:10           ` Michal Novotny
2010-06-21 13:11             ` Keir Fraser
2010-06-21 12:57       ` Michal Novotny
2010-06-21 13:08         ` Keir Fraser [this message]
2010-06-21 13:18           ` Michal Novotny
2010-06-21 13:24             ` Keir Fraser
2010-06-21 13:37               ` Michal Novotny
2010-06-21 13:45                 ` Keir Fraser
2010-06-21 14:02                   ` Michal Novotny
2010-06-21 14:06                     ` Keir Fraser
2010-06-21 14:09                       ` Michal Novotny
2010-06-21 14:50                       ` Michal Novotny
2010-06-21 17:57                         ` Keir Fraser
2010-06-22  5:38                           ` Michal Novotny
2010-06-22  5:58                             ` Keir Fraser
2010-06-22  6:23                               ` Michal Novotny
2010-06-22  6:48                                 ` Jan Beulich
2010-06-22  6:51                                   ` Keir Fraser
2010-06-22  7:12                                     ` Jan Beulich
2010-06-22  7:36                                       ` Keir Fraser
2010-06-22  7:38                                   ` Michal Novotny
2010-06-22 10:01                                   ` Keir Fraser
2010-06-22 10:05                                     ` Michal Novotny
2010-06-22 10:23                                       ` Keir Fraser
2010-06-22 10:53                                         ` Michal Novotny

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=C84522F0.180EE%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=minovotn@redhat.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 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).