xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Michal Novotny <minovotn@redhat.com>
To: xen-devel@lists.xensource.com
Subject: Re: Re: Xen-unstable save error
Date: Mon, 21 Jun 2010 14:47:51 +0200	[thread overview]
Message-ID: <4C1F5F77.2060105@redhat.com> (raw)
In-Reply-To: <C8451D29.180DA%keir.fraser@eu.citrix.com>

On 06/21/2010 02:44 PM, Keir Fraser wrote:
> On 21/06/2010 13:38, "Michal Novotny"<minovotn@redhat.com>  wrote:
>
>    
>> Well, Keir, it does exist:
>>
>> # ls -al /usr/lib64/xen/bin/xc_save
>> -rwxr-xr-x 1 root root 25245 Jun 18 21:37 /usr/lib64/xen/bin/xc_save
>> # /usr/lib64/xen/bin/xc_save
>> xc_save: usage: /usr/lib64/xen/bin/xc_save iofd domid maxit maxf flags
>>
>> Also, when I try to run it manually with the domain running and testing
>> the save it returns:
>>
>> # /usr/lib64/xen/bin/xc_save 56 1 0 0 4
>> /usr/lib64/xen/bin/xc_save: symbol lookup error: undefined symbol:
>> xs_suspend_evtchn_port
>>      
> Ah, the dynamic linker is picking up an old version of libxenstore.
> xs_suspend_evctnn_port was introduced in Xen 3.4.0. I missed that in your
> log-file snippet.
>
>   -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>    
Oh, ok, should it be in /usr/lib then or how to fix it ?

Thanks,
Michal

-- 
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat

  reply	other threads:[~2010-06-21 12:47 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 [this message]
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
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=4C1F5F77.2060105@redhat.com \
    --to=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).