From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NMgbA-0002FQ-8V for qemu-devel@nongnu.org; Mon, 21 Dec 2009 06:38:48 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NMgb5-00027b-KV for qemu-devel@nongnu.org; Mon, 21 Dec 2009 06:38:47 -0500 Received: from [199.232.76.173] (port=49015 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NMgb5-00027J-5m for qemu-devel@nongnu.org; Mon, 21 Dec 2009 06:38:43 -0500 Received: from mx1.redhat.com ([209.132.183.28]:1025) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NMgb4-0007VN-MI for qemu-devel@nongnu.org; Mon, 21 Dec 2009 06:38:42 -0500 Message-ID: <4B2F5E40.6040906@redhat.com> Date: Mon, 21 Dec 2009 13:38:40 +0200 From: Yaniv Kaul MIME-Version: 1.0 Subject: Re: [Qemu-devel] cpuid problem in upstream qemu with kvm 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> In-Reply-To: <4B2F581A.7030206@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: qemu-devel@nongnu.org, Alexander Graf , Gleb Natapov , "Michael S. Tsirkin" On 12/21/2009 1:12 PM, Avi Kivity wrote: > On 12/20/2009 07:18 PM, Michael S. Tsirkin wrote: >> >>>> Hmm, then, shouldn't either kvm or qemu mask features that we do not >>>> emulate well enough to make windows not crash? >>> -cpu host does that already, no? >>> >>> Alex >> I expected so, but Avi here seems to say windows will crash if you >> use a new CPU with it ... > > 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. ( http://www.aumha.org/win5/a/wpa.php ) Y.