From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MR3xT-0001s4-VO for qemu-devel@nongnu.org; Wed, 15 Jul 2009 08:51:40 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MR3xO-0001qs-SY for qemu-devel@nongnu.org; Wed, 15 Jul 2009 08:51:39 -0400 Received: from [199.232.76.173] (port=52929 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MR3xO-0001qj-A8 for qemu-devel@nongnu.org; Wed, 15 Jul 2009 08:51:34 -0400 Received: from wa4ehsobe005.messaging.microsoft.com ([216.32.181.15]:41515 helo=WA4EHSOBE006.bigfish.com) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_ARCFOUR_MD5:16) (Exim 4.60) (envelope-from ) id 1MR3xN-0001Wn-Sx for qemu-devel@nongnu.org; Wed, 15 Jul 2009 08:51:34 -0400 Received: from mail164-wa4 (localhost.localdomain [127.0.0.1]) by mail164-wa4-R.bigfish.com (Postfix) with ESMTP id D80F79201AE for ; Wed, 15 Jul 2009 12:51:26 +0000 (UTC) Received: from svlb1extmailp02.amd.com (unknown [139.95.251.11]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail164-wa4.bigfish.com (Postfix) with ESMTP id 53CC015B0055 for ; Wed, 15 Jul 2009 12:51:25 +0000 (UTC) Received: from svlb1twp01.amd.com ([139.95.250.34]) by svlb1extmailp02.amd.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id n6FCpKNi025480 for ; Wed, 15 Jul 2009 05:51:23 -0700 Received: from SSVLEXBH1.amd.com (ssvlexbh1.amd.com [139.95.53.182]) by svlb1twp01.amd.com (Tumbleweed MailGate 3.5.1) with ESMTP id 299C0884959 for ; Wed, 15 Jul 2009 05:51:05 -0700 (PDT) Message-ID: <4A5DD0B0.7070700@amd.com> Date: Wed, 15 Jul 2009 14:50:56 +0200 From: Andre Przywara MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] CPUID feature bits not saved with migration List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi, while testing the guest multi-core code, I realized that all of the cpuid_* values (like cpuid_ext_features,...) from CPUX86State are not dumped in the migration stream. Is this intentional behavior (to let the user specify other bits in the target?) or has this just been forgotten? Does KVM call the SET_CPUID2 ioctl after or before migration? Regards, Andre. -- Andre Przywara AMD-OSRC (Dresden) Tel: x29712