From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim M Subject: [Bug 1759] Xen 4.0.1 live migration/restore over-writes new hypervisor's boot-time record Date: Wed, 13 Apr 2011 09:25:46 -0700 Message-ID: <20110413162545.GA29815@lumida.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org It was suggested that I submit this to xen-devel in addition to the bug report. I am having the exact problem described in bug 1282. The RedHat 5 errata for Xen 3 describes the problem nicely so I will quote it: xen calculates its running time by adding the hypervisor's up-time to the hypervisor's boot-time record. In live migrations of para-virtualized guests, however, the guest would over-write the new hypervisor's boot-time record with the boot-time of the previous hypervisor. This caused time-dependent processes on the guests to fail This bug was apparently fixed in 3.1.1 (http://xenbits.xen.org/hg/xen-unstable.hg/rev/359707941ae8) but I am having the issue now with Xen 4.0.1 on Debian Squeeze. Did something change with the migrate/restore process so the previous fix no longer applies? Thanks in advance for any help