RE: [Xen-users] Live Migration problems

["Simon Talbot" <simont@xxxxxxxxx>]

A Bit more on this, when the migration has hung, we are left with a tcp
socket session on both the sender and the receiver something along the
following likes:

Sender:
Proto Recv-Q Send-Q Local Address           Foreign Address
State
tcp   143773  87224 217.18.80.18:41967      217.18.80.15:8002
ESTABLISHED

Receiver:
tcp   132612  11540 217.18.80.15:8002       217.18.80.18:41967
ESTABLISHED

So basically broken mid way with large send and receive queues

Simon

Simon Talbot MEng, ACGI 
(Chief Engineer) 
Tel: 020 3161 6001
Fax: 020 3161 6011

The information contained in this e-mail and any attachments are private

and confidential and may be legally privileged. 

It is intended for the named addressee(s) only. If you are not the 
intended recipient(s), you must not read, copy or use the information 
contained in any way. If you receive this email or any attachments in 
error, please notify us immediately by e-mail and destroy any copy you 
have of it. 

We accept no responsibility for any loss or damages whatsoever arising 
in any way from receipt or use of this e-mail or any attachments. This 
e-mail is not intended to create legally binding commitments on our 
behalf, nor do its comments reflect our corporate views or policies.


-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Simon Talbot
Sent: 19 September 2008 10:03
To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Live Migration problems

I have a four node Xen cluster (Version 3.2.0_16718_16-0.3) and have
some problems with live migration.

If for example I have a VM running on node 4 (Say a paravirtualized SLES
Guest) and I perform live migration to node1, then most of the time it
will work fine. But on occasion the source machine gets stuck in the
Migrating-<vm name> state and the destination machine does not start up.
If I manually xm destroy the Migrating-<vm name> on the source node, the
destination completes the handover and runs fine. It is as if the source
node is waiting for some handshake from the destination that never
arrives.

This is fairly random, and I can sometimes migrate forwards and
backwards between Node 4 and Node 1 many (5 or 10) times successfully
before one of the migrations hangs like this.

I have looked at the obvious logs to see if there are any clues as to
why it is hanging, but there is nothing obvious, I am really looking for
some guidance as to which logs and what debugging I can turn on to try
and get to the root cause, and also advice from anyone else who has
experienced this problem as to what if anything they have found out
about it.

Simon

Simon Talbot MEng, ACGI 
(Chief Engineer) 
Tel: 020 3161 6001
Fax: 020 3161 6011

The information contained in this e-mail and any attachments are private

and confidential and may be legally privileged. 

It is intended for the named addressee(s) only. If you are not the 
intended recipient(s), you must not read, copy or use the information 
contained in any way. If you receive this email or any attachments in 
error, please notify us immediately by e-mail and destroy any copy you 
have of it. 

We accept no responsibility for any loss or damages whatsoever arising 
in any way from receipt or use of this e-mail or any attachments. This 
e-mail is not intended to create legally binding commitments on our 
behalf, nor do its comments reflect our corporate views or policies.



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

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