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

RE: [Xen-devel] Re: [BUG 1282] time jump on live migrate root cause & proposed fixes

  • To: "Rik van Riel" <riel@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Thu, 7 Aug 2008 10:22:00 +0800
  • Cc:
  • Delivery-date: Wed, 06 Aug 2008 19:23:10 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acj4MXlEceSHw1zXT/GWQd2OFqaf8gAAmxRQ
  • Thread-topic: [Xen-devel] Re: [BUG 1282] time jump on live migrate root cause & proposed fixes

>From: Rik van Riel
>Sent: 2008年8月7日 10:01
>This really makes me wonder why the guest is getting its
>clock messed up by the difference of system uptimes when
>live migrating from one system to another, between two
>hosts that are NTP synced.
>The reason is that wc_sec + wc_nsec + system_timestamp
>should always be the same across multiple systems, since
>this equals system boot time + uptime.
>Does anybody know why a save/restore or a live migrate
>would mess things up?

Forgot my previous mail just sent out. As you said, ideally
existing implementation looks correct, except uptime is
unexpectedly stamped into some other components like
timer related structures? :-(


Xen-devel mailing list



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