From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [Bug 1759] Xen 4.0.1 live migration/restore over-writes new hypervisor's boot-time record Date: Wed, 13 Apr 2011 19:34:01 +0100 Message-ID: References: <20110413162545.GA29815@lumida.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110413162545.GA29815@lumida.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Tim M , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 13/04/2011 17:25, "Tim M" wrote: > 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? The fix is still there, albeit in a modified form since the restore code has changed quite a bit since Xen 3. Can you reliably repro this, with any PV guest? -- Keir > Thanks in advance for any help > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel