From mboxrd@z Thu Jan  1 00:00:00 1970
From: John Byrne <john.l.byrne@hp.com>
Subject: Migration and CPU type?
Date: Wed, 15 Feb 2006 15:50:56 -0800
Message-ID: <43F3BE60.1040901@hp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org


There are various differences between x86 CPU types that I believe would 
cause a guest to fail after being migrated. Are there checks in the 
migration code to prevent this from happening? Does it check for an 
"incompatible CPU" and fail early, leaving the guest running on the 
source host? If there is a check, what is its nature? (Exact match of 
CPU type/rev or something based on CPU-features?)

Thanks,

John Byrne