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


Re: [Xen-devel] Live migration bug introduced in

To: Philipp Hahn <hahn@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Live migration bug introduced in
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Fri, 28 Jan 2011 08:44:20 +0000
Cc: Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jeremy, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Greg Kroah-Hartman <greg@xxxxxxxxx>, stable@xxxxxxxxxx, Nathan, March <nathan@xxxxxx>
Delivery-date: Fri, 28 Jan 2011 00:45:14 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <201101280747.58019.hahn@xxxxxxxxxxxxx>
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>
Organization: Citrix Systems, Inc.
References: <4D41D3BA.7090602@xxxxxx> <201101280747.58019.hahn@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
(Please don't drop CC's when posting to xen-devel)

On Fri, 2011-01-28 at 06:47 +0000, Philipp Hahn wrote:
> Hello,
> Am Donnerstag 27 Januar 2011 21:21:14 schrieb Nathan March:
> > It looks like a live migration bug may have been introduced in
> ...
> > Note that this isn't consistent at all, I've got 6 dom0's and this only
> > happens when migrating certain directions between certain dom0's:
> Sounds like a problem very similar to mine. Please check if you have the 
> pvclock-going-backwards-problem: 
> <http://lists.xensource.com/archives/html/xen-users/2011-01/msg00375.html>

The fix referenced by that thread (which turns out to be
http://marc.info/?l=linux-kernel&m=128811236726156&w=2) is upstream as
e7a3481c0246c8e45e79c629efd63b168e91fcda but didn't make it to the
stable trees (the resend which was what actually got applied appears to
have accidentally dropped the original's CC:stable@, oops).

This is a fix for 489fb490dbf8dab0249ad82b56688ae3842a79e8 which went
into as 1345126c761f0360dc108973bf73281d51945bc1 so the
timeline fits and the fix seems obviously correct.

Greg, please can you queue e7a3481c0246c8e45e79c629efd63b168e91fcda for
2.6.32.y longterm. The fix is already in 2.6.37-rc1 so its not needed
for the current stable branch.

For completeness 489fb490dbf8dab0249ad82b56688ae3842a79e8 was in
v2.6.35-rc1 and was backported to the 2.6.{32,33,34}.y branches while
e7a3481c0246c8e45e79c629efd63b168e91fcda was in v2.6.37-rc6

(I presume we are not expected to cc all the longterm maintainers for
the various longterm trees and that cc stable@ sufficient)


Xen-devel mailing list