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


[Xen-users] CPU Prerequisites for Live Migrations

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] CPU Prerequisites for Live Migrations
From: "Hoot, Joseph" <joe.hoot@xxxxxxxxxxxxx>
Date: Wed, 20 Oct 2010 11:38:48 -0400
Accept-language: en-US
Acceptlanguage: en-US
Delivery-date: Wed, 20 Oct 2010 08:40:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: ActwbPeAaIYl4d7NRkyMCf/Ec9DrKA==
Thread-topic: CPU Prerequisites for Live Migrations
Hi all,

I'm trying to find documentation to describe what specific CPU flags, models, 
families requirements are needed for live migrations to be "supported."  I have 
found mailing list archives which tend to say things like "should" work or 
"may" work, but nothing that says "is supported." or "is certified."

Basically what I'm wondering is that if I have (2) quad-core cpu's on one 
server and (2) quad-core cpu's on another server -- both have the same family 
and stepping and exact same flags.  The only difference is that the model is 
different.  Is that something that the xen hypervisor typically will support 
when it comes to live migration?


Joseph R. Hoot
Lead System Programmer/Analyst
(w) 716-878-4832
(c) 716-759-HOOT
GPG KEY:   7145F633

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>