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/
Home Products Support Community News


[Xen-users] Paravirtualized DomU clock stops after migrating back

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Paravirtualized DomU clock stops after migrating back
From: S. Ercan Yüzbasioglu <ercan.yuzbasioglu@xxxxxxxxx>
Date: Fri, 20 Feb 2009 12:29:22 +0100
Delivery-date: Fri, 20 Feb 2009 03:30:12 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=z6Mcpk6BcppzLcNCZuTRwmPYm0ikIoAaST9YVwuadX4=; b=PSANaz1JZAVQN8G1uACbt/s8QHOAHIZfWVxAmq97WnaR1kfan2PXL5hO/tzeB8Nu8x 3OuFy2WQtBQ+5AI3BU8hSQwBrTKxtSQXEYrutrScJ0/PT5AcCqoNERjX/aZiXiacILrG qIj0RVdFvq2mFcBqBmGFR0W3bk1Y+YEDihQlc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Hijw6UE/pj3Ok9NGSHMKW6SNY3AsM9+HzmPkm9opPRF8z/f7aS6bo6fBHvgz6PhszF VJZ2xEoIIy9ydxRGPKLwTlDyAeSufM7rrBYoQRdC46Zl53qOF3JEhWbfz5WughIYc2mj Z/4BfF/8ydMj9Apfu8QbZxes4/ONy5Moogoqc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi all,

I think this problem is well known, but I cannot say the same for the solution..

A similar issue was discussed in this mailing list: http://lists.xensource.com/archives/html/xen-users/2008-08/msg01039.html

There are also two bug reports about it, which are marked as resolved, somehow...

However, I cannot solve the problem using the workarounds that are discussed on all those threads.

My problem differs slightly from the ones above:
1. I start the DomU on node1. Its clock works. I migrate the domu from node1 to node2, I open a domu console on node2 and everything is fine. Issuing "date" always gives the right time. However, when I migrate it back to node 1, and open console to domu, I observe that the clock stopped working. "date" gives always the same time, "sleep" won't return, etc.. When I migrate it back to node 2, clock starts working again!

2. This happens after a cold migration too, not necessarily a live one.

I think I did everything recommended on several forums. e.g.:

- On the domu, I set the indepentent wallclock to 1
- I installed ntp client on DomU, I added a couple of ntp servers to ntp.conf (i.e. 0.pool.ntp.org) and ran ntpd before migration.
- Both nodes are syncronized with the same ntp server.

Nothing helped so far.. am I doing something wrong? Please help if you have any clue on this.


Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>