From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NKbgR-0005EN-JM for qemu-devel@nongnu.org; Tue, 15 Dec 2009 12:59:39 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NKbgO-0005CL-0U for qemu-devel@nongnu.org; Tue, 15 Dec 2009 12:59:39 -0500 Received: from [199.232.76.173] (port=53754 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NKbgN-0005CF-LQ for qemu-devel@nongnu.org; Tue, 15 Dec 2009 12:59:35 -0500 Received: from mx1.redhat.com ([209.132.183.28]:35116) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NKbgN-0007fP-6b for qemu-devel@nongnu.org; Tue, 15 Dec 2009 12:59:35 -0500 Date: Tue, 15 Dec 2009 19:56:50 +0200 From: "Michael S. Tsirkin" Subject: Re: [Qemu-devel] cpuid problem in upstream qemu with kvm Message-ID: <20091215175650.GA25529@redhat.com> References: <20091214200002.GA27769@redhat.com> <4B2699BB.1090302@codemonkey.ws> <20091214201049.GD6150@redhat.com> <4B269D99.8080404@codemonkey.ws> <20091214203125.GH6150@redhat.com> <4B26A619.7070503@codemonkey.ws> <20091214211024.GD6100@redhat.com> <4B26B2F3.9080102@codemonkey.ws> <20091215142820.GA23472@redhat.com> <4B27C95E.5080200@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B27C95E.5080200@codemonkey.ws> 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 , avi@redhat.com On Tue, Dec 15, 2009 at 11:37:34AM -0600, Anthony Liguori wrote: > Michael S. Tsirkin wrote: >> I don't think it does: cpuid is an unpriveledged operation, >> is it not? >> > > We (qemu) ask the kernel (kvm.ko) to filter out the features bits from > the cpuid we expose to the guest in order to remove feature bits it > (kvm.ko) does not support. > > Regards, > > Anthony Liguori I see. But unfortunately this bit has multiple meanings for 64/32 bit, kvm does not know whether you will run a 32 bit or a 64 bit program. This is a cpu architecture bug. -- MST