From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] KVMs default CPU type Date: Thu, 25 Jun 2009 11:29:15 +0300 Message-ID: <4A43355B.4080406@redhat.com> References: <20090623162140.GB4379@random.random> <20090624172934.GG14121@shareable.org> <20090624211200.GD15263@random.random> <20090624213944.GD14121@shareable.org> <4A43314E.5050500@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jamie Lokier , Andrea Arcangeli , qemu-devel@nongnu.org, kvm@vger.kernel.org To: Andre Przywara Return-path: Received: from mx2.redhat.com ([66.187.237.31]:56486 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751255AbZFYI2O (ORCPT ); Thu, 25 Jun 2009 04:28:14 -0400 In-Reply-To: <4A43314E.5050500@amd.com> Sender: kvm-owner@vger.kernel.org List-ID: On 06/25/2009 11:11 AM, Andre Przywara wrote: > I think we should go away from using qemu64 as a default for KVM. In > my opinion we should target -cpu host as KVM's default, while in > parallel create a -cpu migrate type (still fiddling with the CPUID > details of that), which takes over the qemu64 role of being some kind > of least common denominator. This should be a family 15 CPU (AMD K8 or > Intel P4) with a constant vendor ID (in my experiments Intel showed > less problems with guests). Since 64bit Windows has a whitelist of > known vendor IDs (AMD, Intel on XP, additionally Via on Win7) we > cannot use a bogus vendor, although this should impose the least > problems. -cpu host may have issues other than migration; for example if you upgrade your host processor guests will notice and perhaps trigger a revalidation. It also means every host offers something slightly different to guests, increasing the test matrix. -- error compiling committee.c: too many arguments to function