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-devel] [Bug 1759] Xen 4.0.1 live migration/restore over-writes new

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [Bug 1759] Xen 4.0.1 live migration/restore over-writes new hypervisor's boot-time record
From: Tim M <bugs@xxxxxxxxxxxxxx>
Date: Wed, 13 Apr 2011 09:25:46 -0700
Delivery-date: Wed, 13 Apr 2011 10:34:09 -0700
Dkim-signature: v=1; q=dns/txt; d=nvbell.net; s=dkim01; i=bradblue@xxxxxxxxxx; a=rsa-sha256; c=relaxed/relaxed; t=1302711948; h=Content-Type:MIME-Version:Message-ID:Subject:To: From:Date; bh=OZq7K7KUdUh1y+8+RGV8CSVewCmGFxCC7sq0B0hewFc=; b=oXo 8bgjm2JMsoEr9rcgUlOzkrqWIM3pxFjouVBaAKCbD0NqcNAx28d4/wW5wc92giMIQwu 22GVy6NtPpu+QZIQ==
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
User-agent: Mutt/1.5.20 (2009-06-14)
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

Xen-devel mailing list