[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Live migration timed out



I also found out that saving a running instance is not possible,
I guess caused by the same 'popen' error:

toor@node-1:/xen$ sudo xm save 1 save.tmp
Error: /usr/lib/xen/bin/xc_save 36 1 0 0 0 failed: popen failed

log:

[2011-09-14 11:06:33 1867] DEBUG (XendCheckpoint:124) [xc_save]: /usr/lib/xen/bin/xc_save 36 1 0 0 0
[2011-09-14 11:06:33 1867] INFO (XendCheckpoint:423) /usr/lib/xen/bin/xc_save: symbol lookup error: /usr/lib/xen/bin/xc_save: undefined symbol: xs_suspend_evtchn_port
[2011-09-14 11:06:33 1867] ERROR (XendCheckpoint:178) Save failed on domain my.lenny (1) - resuming.
Traceback (most recent call last):
 File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendCheckpoint.py", line 146, in save
ÂÂÂ forkHelper(cmd, fd, saveInputHandler, False)
 File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendCheckpoint.py", line 409, in forkHelper
ÂÂÂ raise XendError("%s failed: popen failed" % string.join(cmd))
XendError: /usr/lib/xen/bin/xc_save 36 1 0 0 0 failed: popen failed
[2011-09-14 11:06:33 1867] DEBUG (XendDomainInfo:3117) XendDomainInfo.resumeDomain(1)


Maybe that is also the live migration problem?
What is popen? 'port open' ?

Now I can boot the instance on node-2, I didnt had NFS root write privileges which I could get with
the 'no_root_squash' option in the /etc/exports file. Thank you for that hint!

But the migration is still not working... it is just timing out..

toor@node-1:/xen$ sudo xm migrate 71 192.168.0.3 -l
Error: timed out

the xend.log file says:

[2011-09-14 10:27:31 1679] DEBUG (XendCheckpoint:124) [xc_save]: /usr/lib/xen/bin/xc_save 34 71 0 0 1
[2011-09-14 10:27:31 1679] INFO (XendCheckpoint:423) /usr/lib/xen/bin/xc_save: symbol lookup error: /usr/lib/xen/bin/xc_save: undefined symbol: xs_suspend_evtchn_port
[2011-09-14 10:27:31 1679] ERROR (XendCheckpoint:178) Save failed on domain my.lenny (71) - resuming.
Traceback (most recent call last):
 File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendCheckpoint.py", line 146, in save
ÂÂÂ forkHelper(cmd, fd, saveInputHandler, False)
 File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendCheckpoint.py", line 409, in forkHelper
ÂÂÂ raise XendError("%s failed: popen failed" % string.join(cmd))
XendError: /usr/lib/xen/bin/xc_save 34 71 0 0 1 failed: popen failed
[2011-09-14 10:27:31 1679] DEBUG (XendDomainInfo:3117) XendDomainInfo.resumeDomain(71)
[2011-09-14 10:27:34 1679] ERROR (xmlrpclib2:178) Internal error handling xend.domain.migrate
Traceback (most recent call last):
 File "/usr/local/lib/python2.6/dist-packages/xen/util/xmlrpclib2.py", line 131, in _marshaled_dispatch
ÂÂÂ response = self._dispatch(method, params)
 File "/usr/lib/python2.6/SimpleXMLRPCServer.py", line 418, in _dispatch
ÂÂÂ return func(*params)
 File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomain.py", line 1366, in domain_migrate
ÂÂÂ self._domain_migrate(dominfo, dst, live, port, node)
 File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomain.py", line 1458, in _domain_migrate
ÂÂÂ dsterr = sock.recv(1024)
timeout: timed out


The port 8002 is open on both hosts, connections are possible... the xen config is configured..
I use exactly the same software versions on both hosts..

any ideas?

Thank you!



-- 
Se
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.