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

[Xen-users] Problems with live migrate on xen-testing

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Niraj Tolia <ntolia@xxxxxxxxx>
  • Date: Thu, 7 Apr 2005 15:50:20 -0400
  • Delivery-date: Thu, 07 Apr 2005 19:50:17 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=ldkLQlDtJy9wMtDB/EAnSzv9GzNLT/fxR5L7fVg2hmeFhQ9obUcM5ZlxZTxTsEX01DhyMIWImc3kNwi+j2tXuV3WooFLYYM0RIqi2GJ/YHfXL5ozl9We6h6yad1JnvMXW+J9p9yXKj5js0NVD1mlJ5GnPea+EDvF4jkmcFgIVqM=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I am using xen-testing and trying to migrate a VM between two
machines. However, the migrate command fails with the error "Error:
errors: suspend failed, Callback timed out".

After the error on the source machine, while the VM shows up on xm
list at the destination, xfrd.log (on the destination) shows that its
trying to reload memory pages beyond 100%. The number of memory pages
reloaded keeps on going up until I use 'xm destroy'.

The process of xm save/scp <saved image>/xm restore the machine works
fine though. Any ideas why live migration would not work? The combined
usage of dom0 and domU is around half the physical memory present in
the machine.

The traceback from xend.log

Traceback (most recent call last):
  File "/usr/lib/python2.3/site-packages/twisted/internet/defer.py",
line 308, in _startRunCallbacks
  File "/usr/lib/python2.3/site-packages/twisted/internet/base.py",
line 82, in cancel
    raise error.AlreadyCalled
AlreadyCalled: Tried to cancel an already-called event.

xfrd.log on the sender is full of "Retry suspend domain (120)" before
it says "Unable to suspend domain. (120)" and "Domain appears not to
have suspended: 120".



Xen-users mailing list



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