WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Verify memory image error when live migration vm

To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Verify memory image error when live migration vm
From: "zhangxiang" <zhangxiang@xxxxxxxxxx>
Date: Mon, 14 Dec 2009 17:07:06 +0800
Delivery-date: Mon, 14 Dec 2009 01:07:30 -0800
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
Hello, everyone!
   I am testing live migration of xen virtual machine on my platform. I find that when I verifing the memory image of migrated VM, there are always some memory
pages that different between source and destination, even the migrated vm is idle. It was shown below:
  
Entering page verify mode
[2009-12-14 16:55:44 3659] INFO (XendCheckpoint:403) ************** pfn=3f00c type=0 gotcs=9a8be84c538fca80 actualcs=9a8b161de63578e2
[2009-12-14 16:55:44 3659] INFO (XendCheckpoint:403) 0: 3000020000ff3333 3000d4277d483000
[2009-12-14 16:55:44 3659] INFO (XendCheckpoint:403) 1: 4500007464c848 45000844617f48
[2009-12-14 16:55:44 3659] INFO (XendCheckpoint:403) ************** pfn=3f00d type=0 gotcs=d23bab16a683bfcd actualcs=223aa70eca181ad8
[2009-12-14 16:55:44 3659] INFO (XendCheckpoint:403) 0: 3000020000ff3333 e000ffffffffffff
[2009-12-14 16:55:44 3659] INFO (XendCheckpoint:403) 1: 10000007464c848 100060801f95281
[2009-12-14 16:55:44 3659] INFO (XendCheckpoint:403) ************** pfn=3f01a type=0 gotcs=31ebd12839f7da2f actualcs=5b59041205544e8f
[2009-12-14 16:55:44 3659] INFO (XendCheckpoint:403) 0: 3000ffffffffffff 3000faff7f5e0001
[2009-12-14 16:55:44 3659] INFO (XendCheckpoint:403) 2: 11800000de7c4e00 11010000ae7ba300
[2009-12-14 16:55:44 3659] INFO (XendCheckpoint:403) 3: a0afc4d0a0ab15b ffeffc4d0a0a9bf5
[2009-12-14 16:55:44 3659] INFO (XendCheckpoint:403) ************** pfn=3f046 type=0 gotcs=31ebd12838f7d83f actualcs=b6ff0f833122f1d7
[2009-12-14 16:55:44 3659] INFO (XendCheckpoint:403) 0: e00004090a5e0001 3000faff7f5e0001
[2009-12-14 16:55:44 3659] INFO (XendCheckpoint:403) 1: 45000801f95281 450008b0155b48
[2009-12-14 16:55:44 3659] INFO (XendCheckpoint:403) 2: 1101004000002f00 11010000af7ba300
[2009-12-14 16:55:44 3659] INFO (XendCheckpoint:403) 3: ae007660a0a9f20 ffeffc4d0a0a9af5
 
  The version of Xen is 3.3.1, Linux-2.6.18.8. The CPU of my platform is AMD Opteron 2216, and the VM is 64-bit. The migrated VM could continue to run
at destination, even that some pages are different.
  I donot know how to explan this phenomenon, it really troubles me a lot.
  Thank you very much for your help!
 
  Xiang Zhang
  Dec 14th, 2009

 National Research Center for Intelligent Computing System
 Institute of Computing Technology
 Chinese Academy of Sciences
 P.O. Box 2704, Beijing 100190, P. R. China
 Tel: +86-10-6260 1009
---------------------------------------------------------------------
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Verify memory image error when live migration vm, zhangxiang <=