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

Re: [Xen-users] Re: [Xen-devel] xm migrate --live fails

To: Walter Robert Ditzler <ditwal001@xxxxxxxxx>
Subject: Re: [Xen-users] Re: [Xen-devel] xm migrate --live fails
From: Shriram Rajagopalan <rshriram@xxxxxxxxx>
Date: Wed, 3 Aug 2011 19:34:07 -0400
Cc: Nathan March <nathan@xxxxxx>, Pasi Kärkkäinen <pasik@xxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 03 Aug 2011 16:36:25 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=fM+XmU/NWZmjeRd4VcFgKFzGDlYnPfgt6I5QbzPNwAM=; b=fnzEFSHYxiEPwxdTDVWIvaTtAhdR9amGcfGkeHWmt2U2UfmNCaL1QTMcb8rjhc6iQx iBp7K4FXSRT84PYK9t+zTJfzJbKP2suFmDJ0aINvCt4cKB3ka/vfVnHfBF31Y1fauU5j X4TUAcwHLx9qWwypnVaVMpCkfxi3mgR917z2k=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <!&!AAAAAAAAAAAYAAAAAAAAAOJK0u4CH31Kl5v1RPAzyrZCgQAAEAAAAMz4IpLAXL9MkcBkTX57Ig8BAAAAAA==@xxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <!&!AAAAAAAAAAAYAAAAAAAAAOJK0u4CH31Kl5v1RPAzyrZCgQAAEAAAALMYETG7089CgH5yGIJshxoBAAAAAA==@xxxxxxxxx> <20110727165813.GY32373@xxxxxxxxxxx> <!&!AAAAAAAAAAAYAAAAAAAAAOJK0u4CH31Kl5v1RPAzyrZCgQAAEAAAALIJH8piR1VAvWJKgo8HtMUBAAAAAA==@xxxxxxxxx> <20110728004530.GA32373@xxxxxxxxxxx> <4E30BE42.4050304@xxxxxx> <CAP8mzPOr1xa0HRqihE9PA_zcFkkZuBb-AxRRGCYmYTv0P1gNZw@xxxxxxxxxxxxxx> <!&!AAAAAAAAAAAYAAAAAAAAAOJK0u4CH31Kl5v1RPAzyrZCgQAAEAAAAMz4IpLAXL9MkcBkTX57Ig8BAAAAAA==@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I am confused. Are you asking about "xl migrate --live" or "xm migrate --live" ?
The email subject says "xm migrate --live fails" and you state

 

xm migrate works now, since I reinstalled my backup host, happened already 2nd time!

great!. so that solves your problem. :)
 

 

xl migrate, never worked, it goes up to the end, 100%, then an error which says:

This i have no idea about. 

 

***

root@srv-ldeb-xen001:/etc/xen# xl migrate --live server02 sync2

option `-' not supported.

option `l' not supported.

option `i' not supported.

option `v' not supported.

root@sync2's password:

migration target: Ready to receive domain.

Saving to migration stream new xl format (info 0x0/0x0/804)

Loading new save file incoming migration stream (new xl fmt info 0x0/0x0/804)

Savefile contains xl domain config

WARNING: ignoring "kernel" directive for HVM guest. Use "firmware_override" instead if you really want a non-default firmware

WARNING: ignoring device_model directive.

WARNING: Use "device_model_override" instead if you really want a non-default device_model

xc: Saving memory: iter 0 (last sent 0 skipped 0): 1048576/1048576  100%

xc: Saving memory: iter 1 (last sent 133120 skipped 0): 1048576/1048576  100%

xc: Saving memory: iter 2 (last sent 0 skipped 0): 1048576/1048576  100%

libxl: error: libxl_dom.c:604:libxl__domain_save_device_model: Unable to stat qemu save file

 

migration sender: libxl_domain_suspend failed (rc=-3)

xc: error: 0-length read: Internal error

xc: error: read_exact_timed failed (read rc: 0, errno: 0): Internal error

xc: error: Error reading QEMU signature (0 = Success): Internal error

xc: error: error buffering image tail: Internal error

libxl: error: libxl_dom.c:363:libxl__domain_restore_common: restoring domain: Resource temporarily unavailable

libxl: error: libxl_create.c:483:do_domain_create: cannot (re-)build domain: -3

libxl: error: libxl.c:733:libxl_domain_destroy: non-existant domain 3

libxl: info: libxl_exec.c:125:libxl_report_child_exitstatus: migration target process [4462] exited with error status 253

Migration failed, resuming at sender.

***

 

***

root@srv-ldeb-xen001:/etc/xen# xl list

Name                                        ID   Mem VCPUs      State   Time(s)

Domain-0                                     0  1024     4     r-----   12057.7

server01                                     1  2047     1     -b----     358.3

server02                                     2   511     1     ---ss-      78.2

***

 

 

thanks walter

 

From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Shriram Rajagopalan
Sent: Donnerstag, 28. Juli 2011 16:26
To: Nathan March
Cc: Walter Robert Ditzler; xen-users@xxxxxxxxxxxxxxxxxxx; Pasi Kärkkäinen
Subject: [Xen-users] Re: [Xen-devel] xm migrate --live fails

 


xc: error: Error when writing to state file (4a) (errno 104) (104 =
Connection reset by peer): Internal error

This is what bothers me. Any firewall rules or such?
try to first telnet to the peer
telnet <host> 8002
if you can telnet to that port, then please check the target host's xend.log
for any errors.

On Wed, Jul 27, 2011 at 9:41 PM, Nathan March <nathan@xxxxxx> wrote:

On 7/27/2011 5:45 PM, Pasi Kärkkäinen wrote:

On Wed, Jul 27, 2011 at 09:38:16PM +0200, Walter Robert Ditzler wrote:

pasi,

sory for the email before, save/restore works! I mistyped safe instead of
save, been already a long day :-)


Ok, so save/restore works, but live migration doesn't..

-- Pasi

 

Have you configured the relation server & hosts in /etc/xen/xend-config.sxp?

(xend-relocation-server yes)
(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')

Check /var/log/xen/ as well for some extra info. Also, this is more suited for the xen-users mailing list :)

- Nathan



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

 

to that issue i can still say:

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>