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-users

Re: [Xen-users] xen save error

To: "Cole, Ray" <Ray_Cole@xxxxxxx>
Subject: Re: [Xen-users] xen save error
From: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Date: Thu, 15 Sep 2005 02:18:56 +0100
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Steven.Hand@xxxxxxxxxxxx, bryant.johan@xxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 15 Sep 2005 01:16:58 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: Message from "Cole, Ray" <Ray_Cole@xxxxxxx> of "Wed, 14 Sep 2005 15:27:30 CDT." <4C38B972143E1A4BA2D5E1F12104ECA606F34CED@xxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
>I can get xen-2.0-testing to fail on live migrations with virtually no
load about 10% of the time with live migration :-)  Seems it becomes
>unable to suspend the user domain kernel - kernel gets the message, but
>never gets a chance to process it.  I'm not saying 2.0-testing won't
>resolve the problem John is seeing, but I'm not sure I would quite make
>the statement that it has been 'battle tested' :-)

So as the one who did the 'battle testing' I should speak up :^) 

I did test tens of thousands of save/restore/migrations, but on 2.0.7-patch
i.e. on a version of the 2.0.7 tree with the save/restore fixes applied. 
This was not checked in directly to 2.0.7 since we aim to filter stuff 
through 2.0-testing and make a release that way. 

So it's extremely interesting to us if you have observed errors in 2.0-testing
since this might mean that something else is to blame (e.g. the upgrade from
2.6.11 to 2.6.12). This will delay our release of 2.0.8 which we were hoping
to do RSN. 

Can you possibly post some more details about what you observe? And what is 
in xend.log / xend-debug.log / xfrd.log? Is there a relatively small test
case that allows you to reproduce? 


thanks, 

S.

(p.s. as to the OP, I'm pretty sure the error he was seeing is fixed in 
both 2.0.7 and 2.0-testing) 

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