From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NMNqE-0006pm-0l for qemu-devel@nongnu.org; Sun, 20 Dec 2009 10:37:06 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NMNq9-0006oV-G1 for qemu-devel@nongnu.org; Sun, 20 Dec 2009 10:37:05 -0500 Received: from [199.232.76.173] (port=41833 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NMNq9-0006oQ-7N for qemu-devel@nongnu.org; Sun, 20 Dec 2009 10:37:01 -0500 Received: from mx1.redhat.com ([209.132.183.28]:30353) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NMNq8-00089t-QC for qemu-devel@nongnu.org; Sun, 20 Dec 2009 10:37:01 -0500 Message-ID: <4B2E4499.6010202@redhat.com> Date: Sun, 20 Dec 2009 17:36:57 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] cpuid problem in upstream qemu with kvm References: <20091214193541.GA6150@redhat.com> <4B269596.1050103@codemonkey.ws> <20091214194432.GC6150@redhat.com> <4B2698A9.9090107@codemonkey.ws> <20091214200002.GA27769@redhat.com> <4B2699BB.1090302@codemonkey.ws> <20091214201049.GD6150@redhat.com> <4B269D99.8080404@codemonkey.ws> <4B2DF334.6030208@redhat.com> <4B2E3943.9020802@codemonkey.ws> <4B2E3AC5.3040200@redhat.com> <4B2E43BA.7030404@codemonkey.ws> In-Reply-To: <4B2E43BA.7030404@codemonkey.ws> 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: Anthony Liguori Cc: qemu-devel@nongnu.org, Gleb Natapov , "Michael S. Tsirkin" On 12/20/2009 05:33 PM, Anthony Liguori wrote: >> - casual (non-management-app-using) users will start seeing problems >> with Windows guests unless they change their command lines > > > Assuming their migrating across different CPU types. > I was thinking about upgrading their host cpu. I doubt you'd live migrate without a management app. >> - management apps really have to take cpuid into account now >> (previously, it was just a good idea) > > Yes. I think we probably should have a management app writers guide > that spells out all of the quirks and best practices that we often > discuss here and assume that management app writers are going to follow. Definitely. -- error compiling committee.c: too many arguments to function