From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NMiMs-0007u2-7A for qemu-devel@nongnu.org; Mon, 21 Dec 2009 08:32:10 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NMiMn-0007jx-74 for qemu-devel@nongnu.org; Mon, 21 Dec 2009 08:32:09 -0500 Received: from [199.232.76.173] (port=49594 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NMiMm-0007jd-W2 for qemu-devel@nongnu.org; Mon, 21 Dec 2009 08:32:05 -0500 Received: from mx1.redhat.com ([209.132.183.28]:54348) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NMiMm-0005kM-Jh for qemu-devel@nongnu.org; Mon, 21 Dec 2009 08:32:04 -0500 Message-ID: <4B2F78CF.6050705@redhat.com> Date: Mon, 21 Dec 2009 14:31:59 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <4B2698A9.9090107@codemonkey.ws> <20091214200002.GA27769@redhat.com> <4B2699BB.1090302@codemonkey.ws> <20091214201049.GD6150@redhat.com> <4B269D99.8080404@codemonkey.ws> <4B2DF334.6030208@redhat.com> <20091220155101.GB31257@redhat.com> <4B2E49E5.6050709@redhat.com> <20091220165612.GC31257@redhat.com> <20091220171822.GD31257@redhat.com> <4B2F581A.7030206@redhat.com> <4B2F5E40.6040906@redhat.com> In-Reply-To: <4B2F5E40.6040906@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: cpuid problem in upstream qemu with kvm List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Yaniv Kaul Cc: Alexander Graf , "Michael S. Tsirkin" , Avi Kivity , Gleb Natapov , qemu-devel@nongnu.org >> No, Windows tries to detect changes in your hardware and assumes that >> if too many things change, you might be a pirate and requires you to >> phone their offices to re-authenticate. > > 'Just' the CPU is not big deal. Might hit you with two 'bad' points. > Network interface + CPU will require re-activation. I think the problem is only for networked images. For normal images, it would be the same if you were running Windows natively---upgrade CPU, and you risk having to do reactivation. For networked images, does changing CPU twice count as changing one thing? If so that's not too bad, not many things are likely to change in a VM beyond the CPU. Besides, if you have networked images, it's relatively likely that you're doing it for a company, hence that you have some kind of MSDN subscription which grants you unlimited activations for a given product key. Paolo