From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NSqmT-0007v2-4E
	for qemu-devel@nongnu.org; Thu, 07 Jan 2010 06:43:57 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NSqmO-0007sl-90
	for qemu-devel@nongnu.org; Thu, 07 Jan 2010 06:43:56 -0500
Received: from [199.232.76.173] (port=33828 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NSqmO-0007sa-2H
	for qemu-devel@nongnu.org; Thu, 07 Jan 2010 06:43:52 -0500
Received: from mx1.redhat.com ([209.132.183.28]:56399)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <dlaor@redhat.com>) id 1NSqmN-0008ND-5S
	for qemu-devel@nongnu.org; Thu, 07 Jan 2010 06:43:51 -0500
Message-ID: <4B45C90C.1000507@redhat.com>
Date: Thu, 07 Jan 2010 13:44:12 +0200
From: Dor Laor <dlaor@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] cpuid problem in upstream qemu with kvm
References: <4B30EFDF.4060202@codemonkey.ws>	<4B31F1BA.10005@redhat.com>	<4B43D4E2.9050102@codemonkey.ws>	<4B4402B1.1030605@redhat.com>	<4B448F36.8030605@codemonkey.ws>	<4B449467.4070606@redhat.com>	<4B4494FC.1080907@codemonkey.ws>	<4B449608.7040102@redhat.com>	<F67360FA-5DDF-41A1-87AA-726D13A87AD5@suse.de>	<4B4496E9.2030201@redhat.com>	<20100106142231.GF2248@redhat.com>	<4B449EE7.4050401@redhat.com>	<4B44A2C6.4050504@redhat.com>
	<4B44A965.9040300@codemonkey.ws>	<4B459550.6000202@redhat.com>
	<4B4598BC.4000206@redhat.com>	<4B45A536.1070300@redhat.com>
	<4B45A851.5000401@redhat.com> <4B45AC18.8040003@redhat.com>
	<4B45C7EB.1010501@codemonkey.ws>
In-Reply-To: <4B45C7EB.1010501@codemonkey.ws>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: dlaor@redhat.com
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm-devel <kvm@vger.kernel.org>, Gleb Natapov <gleb@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>, John Cooper <john.cooper@redhat.com>, Alexander Graf <agraf@suse.de>, qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>

On 01/07/2010 01:39 PM, Anthony Liguori wrote:
> On 01/07/2010 03:40 AM, Dor Laor wrote:
>>> There's no simple solution except to restrict features to what was
>>> available on the first processors.
>>
>> What's not simple about the above 4 options?
>> What's a better alternative (that insures users understand it and use
>> it and guest msi and even skype application is happy about it)?
>
> Even if you have -cpu Nehalem, different versions of the KVM kernel
> module may additionally filter cpuid flags.
>
> So if you had a 2.6.18 kernel and a 2.6.33 kernel, it may be necessary
> to say:
>
> (2.6.33) qemu -cpu Nehalem,-syscall
> (2.6.18) qemu -cpu Nehalem

Or let qemu do it automatically for you.

>
> In order to be compatible.
>
> Regards,
>
> Anthony Liguori
>