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-devel

[Xen-devel] Migrated domUs hangs

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Migrated domUs hangs
From: Cédric Schieli <cschieli@xxxxxxxxx>
Date: Sat, 2 Oct 2010 14:22:04 +0200
Delivery-date: Sat, 02 Oct 2010 05:22:59 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=6HtykfRPEp3GGWvDaFpWxXC280p2WQQVhbjhsARLI/U=; b=uMjS0+NlEcgRALlCdsLzLlfaeW6svHQr/LZDOVUKwzuiprC/Pw437xEElyIs9Lcqt8 gqgGk5Y5ugVQhUJfg4zW3s1zY7mg7NlWeKB6t0U/6rym15gEjDCNJSXjKLOE8F/XOC8f mCU0/XV9SeDgh9yV0fw5SmoshXQRCFii0N8dM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=PnGPztxBZ0+uFcAgkLxVd+9eVQopapWw6twx82DxDumRy5oAkZ9xUeAYZXyVJFWrXj xLXwNAZdVeyi4EhTP4DvYbKwYF3k+gt5081kjA113KVw7Gpn9FfxDhiQACuR/xMBNkvK gs7p3XeCDzZZwP9FwWApRQrEvN7m0nXqx9uIk=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hello,

I have a live migration problem on my setup. Migrated DomUs hang, but continue as normal when migrated back.

Both nodes are i386 Debian Squeeze dom0 (xen 4.0.1 + pvops0 2.6.32-5-xen-686)
Node A is a 32bits 2.4 Ghz Pentium4, node B is a 32bits 2.0 Ghz Celeron.

DomUs are Debian Squeeze (2.6.32-5-xen-686 >= 2.6.32-22 or 2.6.32-5-686-bigmem >= 2.6.32-22) and Ubuntu Maverick (2.6.35-22-generic-pae)
They will hang when migrated onto the node which has the lowest uptime, even if it is the node where the domain was initially created. If I migrate them back, they continue running as if nothing had happened.

Debian DomUs with 2.6.32-5-xen-686 = 2.6.32-21 don't have the problem. Reverting "x86, paravirt: Add a global synchronization point for pvclock" (489fb490dbf8dab0249ad82b56688ae3842a79e8) on Debian's 2.6.32-5-xen-686 = 2.6.32-23 also works.
And finally, passing clocksource=tsc to DomUs won't change anything.

Is this a known problem ? May it be specific to my setup ?

TIA,
Cédric Schieli
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Migrated domUs hangs, Cédric Schieli <=