WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Migration fails!!!

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Migration fails!!!
From: "andrea15@xxxxxx" <andrea15@xxxxxx>
Date: Fri, 20 Jul 2007 09:57:36 +0100 (GMT+01:00)
Delivery-date: Fri, 20 Jul 2007 01:55:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Reply-to: "andrea15@xxxxxx" <andrea15@xxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi all,
I'm having problem testing migration (live and regular).
I've 
activated a relocation server on both my machines (fisrt one is a 
fedora5, second one is a debian), chosen 8002 as relocation port and 
allowed connection from the Internet.
(xend-http-server yes)
#(xend-
unix-server yes)
(xend-relocation-server yes)
(xend-port 8000)
(xend-
relocation-port 8002)
(xend-address '')
#(xend-address localhost)
(xend-
relocation-address '')
(xend-relocation-hosts-allow '')
#(xend-
relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')
etc.....
I rebooted my machines when edited xend-config.sxp.
My 
Machines are on the same L2 subnet and there are not route problem 
between them.
 
that's what prompts me when I try migrating:
[root@localhost fedora6]# xm migrate 13 143.225.229.137
Error: 
/usr/lib/xen/bin/xc_save 18 13 0 0 0 failed
Usage: xm migrate <Domain> 
<Host>

It seems a problem when saving VM state. However if I try with 
xm save I've no problem with it...I can also restore VM execution from 
the file generated with xm save.
Here is the xend.log:
[2007-07-18 08:
59:38 xend 3634] 
DEBUG (XendCheckpoint:83) [xc_save]:
/usr/lib/xen/bin/xc_save 18 13 0 0 0
[2007-07-18 08:59:39 xend 3634] 
DEBUG (XendCheckpoint:209) suspend
[2007-07-18 08:59:39 xend 3634] 
DEBUG (XendCheckpoint:86) In saveInputHandler suspend
[2007-07-18 08:
59: 39 xend 3634] 
DEBUG (XendCheckpoint:88) Suspending 13 ...
[2007-07-
18 08:59:39 xend.XendDomainInfo 3634] 
DEBUG (XendDomainInfo:933) 
XendDomainInfo.handleShutdownWatch
[2007-07-18 08:59:39 xend.
XendDomainInfo 3634] 
DEBUG (XendDomainInfo:933) XendDomainInfo.
handleShutdownWatch
[2007-07-18 08:59:39 xend.XendDomainInfo 3634] 
INFO (XendDomainInfo:892) Domain has shutdown: name=migrating-fedora6 
id=13 
reason=suspend.
[2007-07-18 08:59:39 xend 3634] 
INFO 
(XendCheckpoint: 93) Domain 13 suspended.
[2007-07-18 08:59:39 xend 
3634] 
DEBUG (XendCheckpoint:98) Written done
[2007-07-18 08:59:39 xend 
3634] 
ERROR (XendCheckpoint:236) Had 0 unexplained entries in p2m 
table
[2007-07-18 08:59:39 xend 3634] ERROR (XendCheckpoint:236) Saving 
memory pages: 
iter 1 0%Error when writing to state file (2): 32
[2007-
07-18 08:59: 39 xend 3634] 
ERROR (XendCheckpoint:236) Save exit rc=1
[2007-07-18 08: 59:39 xend 3634] 
ERROR (XendCheckpoint:106) Save 
failed on domain fedora6 (13).
Traceback (most recent call last): File 
"/usr/lib/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 
100, in save
forkHelper(cmd, fd, saveInputHandler, False)
File 
"/usr/lib/python2.4/site-packages/xen/xend/XendCheckpoint.py",line 227, 
in forkHelper
raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib/xen/bin/xc_save 18 13 0 0 0 failed

however, I 
haven't yet used a networked solution for my disk images.
they're 
stored on local hard disk.I wanted to be sure of my configuration 
before, facing the problem after.
So I don't expect migration 
successfully terminates, but at least begins...
But I don't think It's 
the reason for which migration fails...
Let me read good news!!!
Andrea 
Sibilia

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Migration fails!!!, andrea15@xxxxxx <=