From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NNDeu-0004gn-9z for qemu-devel@nongnu.org; Tue, 22 Dec 2009 17:56:52 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NNDep-0004eB-KM for qemu-devel@nongnu.org; Tue, 22 Dec 2009 17:56:51 -0500 Received: from [199.232.76.173] (port=34015 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NNDep-0004dz-CM for qemu-devel@nongnu.org; Tue, 22 Dec 2009 17:56:47 -0500 Received: from mail2.shareable.org ([80.68.89.115]:52625) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NNDeo-0006iD-RH for qemu-devel@nongnu.org; Tue, 22 Dec 2009 17:56:47 -0500 Date: Tue, 22 Dec 2009 22:56:44 +0000 From: Jamie Lokier Subject: Re: [Qemu-devel] Re: cpuid problem in upstream qemu with kvm Message-ID: <20091222225644.GC19806@shareable.org> References: <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> <4B2F78CF.6050705@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B2F78CF.6050705@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Gleb Natapov , "Michael S. Tsirkin" , qemu-devel@nongnu.org, Alexander Graf , Yaniv Kaul , Avi Kivity Paolo Bonzini wrote: > > >>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. Are you joking? Even as a casual users, when would you ever run Windows without networking these days???! I don't think you can even buy a computer without networking any more :-) Even just to transfer files from host to guest, you'll typically use a network. Or do you mean something else by "networked images" in a company context? Fwiw, when I have done Windows migrations for companies, they never have MSDN subscriptions (and neither do I :-) They have purchased Windows with the machines, and later they want to migrate those machines into VMs. No hint of MSDN anywhere, why would they? -- Jamie