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

Re: [Xen-devel] Migrate/Save of 32-bit domU Broken on Xen 3.1.2 64-bit d

To: Kurt Hackel <kurt.hackel@xxxxxxxxxx>
Subject: Re: [Xen-devel] Migrate/Save of 32-bit domU Broken on Xen 3.1.2 64-bit dom0
From: Joshua West <jwest@xxxxxxxxxxxx>
Date: Fri, 18 Jan 2008 17:05:43 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 18 Jan 2008 14:07:14 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20080118060148.GA11174@xxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <47900D35.9000203@xxxxxxxxxxxx> <20080118060148.GA11174@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.9 (X11/20071031)
Hi Kurt & Xen Developers,

I applied those two patches to Xen 3.1.3-rc1. Unfortunately, the issue still persists. xc_save fails and therefore save/migrate doesn't work. However, I did receive a different error message this time. Here's the snippit from /var/log/xen/xend.log:

#----------------------------------------------------------#
[2008-01-18 16:57:06 6774] DEBUG (XendCheckpoint:88) [xc_save]: /usr/lib64/xen/bin/xc_save 24 1 0 0 0
[2008-01-18 16:57:06 6774] DEBUG (XendCheckpoint:333) suspend
[2008-01-18 16:57:06 6774] DEBUG (XendCheckpoint:91) In saveInputHandler suspend
[2008-01-18 16:57:06 6774] DEBUG (XendCheckpoint:93) Suspending 1 ...
[2008-01-18 16:57:06 6774] DEBUG (XendDomainInfo:451) XendDomainInfo.shutdown(suspend) [2008-01-18 16:57:06 6774] DEBUG (XendDomainInfo:991) XendDomainInfo.handleShutdownWatch [2008-01-18 16:57:06 6774] DEBUG (XendDomainInfo:991) XendDomainInfo.handleShutdownWatch [2008-01-18 16:57:06 6774] INFO (XendDomainInfo:1179) Domain has shutdown: name=migrating-rhel5-test id=1 reason=suspend.
[2008-01-18 16:57:06 6774] INFO (XendCheckpoint:98) Domain 1 suspended.
[2008-01-18 16:57:06 6774] DEBUG (XendCheckpoint:107) Written done
[2008-01-18 16:57:06 6774] INFO (XendCheckpoint:362) Had 0 unexplained entries in p2m table [2008-01-18 16:57:08 6774] INFO (XendCheckpoint:362) Saving memory pages: iter 1 15%ERROR Internal error: Fatal PT race (pfn 853, type 20000000)
[2008-01-18 16:57:08 6774] INFO (XendCheckpoint:362) Save exit rc=1
[2008-01-18 16:57:08 6774] ERROR (XendCheckpoint:140) Save failed on domain rhel5-test (1).
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 109, in save
   forkHelper(cmd, fd, saveInputHandler, False)
File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 350, in forkHelper
   raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_save 24 1 0 0 0 failed
[2008-01-18 16:57:08 6774] DEBUG (XendDomainInfo:1802) XendDomainInfo.resumeDomain(1) [2008-01-18 16:57:08 6774] DEBUG (XendCheckpoint:143) XendCheckpoint.save: resumeDomain
#----------------------------------------------------------#

Just to make sure the patches aren't the cause of this new error message, I'm going to see what happens with Xen 3.1.3-rc1 w/o patches.

Kurt, Keir, everybody else... any ideas as to why "xm save" (and thus "xm migrate") of 32-bit domU's does not work on 64-bit dom0's? Has anybody found this to be successful in the past?

Thanks.

Kurt Hackel wrote:
Hi Joshua,

Can you try the two attached patches?  This should apply to 3.1.3-pre.
These take care of the 32-bit dom0/64-bit domU case, but also should
have some affect on your 64-bit dom0/32-bit domU.
Thanks
kurt

------------------------------------------------------------------------

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


--
Joshua West
Systems Engineer
Brandeis University
http://www.brandeis.edu


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel