Re: Re: Xen-unstable save error

[Michal Novotny <minovotn@redhat.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
>    
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:

[2010-06-21 14:52:22 6151] DEBUG (XendCheckpoint:126) [xc_save]: 
/usr/lib64/xen/bin/xc_save 57 1 0 0 4
[2010-06-21 14:52:22 6151] ERROR (XendCheckpoint:180) Save failed on 
domain rhel5-32fv-stubdom (1) - resuming.
Traceback (most recent call last):
   File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", 
line 148, in save
     forkHelper(cmd, fd, saveInputHandler, False)
   File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", 
line 398, in forkHelper
     raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_save 57 1 0 0 4 failed
[2010-06-21 14:52:22 6151] DEBUG (XendDomainInfo:3131) 
XendDomainInfo.resumeDomain(1)

and when I run xc_save manually it's returning segmentation fault:

  gdb -arg /usr/lib64/xen/bin/xc_save 57 1 0 0 4
GNU gdb Fedora (6.8-27.el5)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...
(gdb) run
Starting program: /usr/lib64/xen/bin/xc_save 57 1 0 0 4
[Thread debugging using libthread_db enabled]
[New Thread 0x7f6490b9d6e0 (LWP 6785)]

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00000000004014f5 in main (argc=<value optimized out>, 
argv=0x7fffb5942ac8) at xc_save.c:192
(gdb) up
#1  0x00000000004014f5 in main (argc=<value optimized out>, 
argv=0x7fffb5942ac8) at xc_save.c:192
192             port = xs_suspend_evtchn_port(si.domid);

So I'm sorry, I was wrong about the line. This is from some other file. 
According to strace the "/usr/lib64/libxenctrl.so.4.0" (which has been 
built today) is loaded there but "objdump -x 
/usr/lib64/libxenctrl.so.4.0 | grep xs_" doesn't return anything.

Any ideas now?

Michal

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