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] DomU crash during migration when suspendingsource domain

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] DomU crash during migration when suspendingsource domain
From: "Graham, Simon" <Simon.Graham@xxxxxxxxxxx>
Date: Wed, 14 Feb 2007 08:57:54 -0500
Delivery-date: Wed, 14 Feb 2007 05:58:14 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdP6h4+HveIAzruQ3+gt7NQNapEGwANqzaeAADJUVAAAHIl2wAGcwGg
Thread-topic: [Xen-devel] DomU crash during migration when suspendingsource domain
> Are you migrating between unlike boxes? My guess is that the original
> box
> has processors supporting cacheinfo cpuid leaves and the target box
> does
> not. Migrating to older less-capable CPUs is definitely hit-and-miss
> I'm
> afraid. It really is best not to do it!
>

I think this is indeed what is happening -- supporting this is kind of
important for HA/FT - you need to be able to keep the domains running
when upgrading/replacing hardware.

I guess I'm still a tad confused, but presumably the CPU_DEAD processing
is not completely uninitializing the cache info (it seems to me that if
it discarded the cache info and NULL's the pointer in the CPU_DEAD
processing then it should get recreated when the CPU_ONLINE is done -
presumably there is some path where this is not done when it should be.

I'll do some more digging and get back with a proposed fix.
Simon
 

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