From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NMhFi-0003Up-Qx for qemu-devel@nongnu.org; Mon, 21 Dec 2009 07:20:42 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NMhFd-0003H4-Hx for qemu-devel@nongnu.org; Mon, 21 Dec 2009 07:20:41 -0500 Received: from [199.232.76.173] (port=48926 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NMhFd-0003Gr-D6 for qemu-devel@nongnu.org; Mon, 21 Dec 2009 07:20:37 -0500 Received: from mx1.redhat.com ([209.132.183.28]:53131) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NMhFd-0007UN-1P for qemu-devel@nongnu.org; Mon, 21 Dec 2009 07:20:37 -0500 Date: Mon, 21 Dec 2009 14:17:51 +0200 From: "Michael S. Tsirkin" Subject: Re: [Qemu-devel] cpuid problem in upstream qemu with kvm Message-ID: <20091221121751.GE6309@redhat.com> References: <20091220155101.GB31257@redhat.com> <4B2E49E5.6050709@redhat.com> <20091220165612.GC31257@redhat.com> <20091220171822.GD31257@redhat.com> <4B2F581A.7030206@redhat.com> <20091221111856.GA6309@redhat.com> <4B2F645F.5080506@redhat.com> <20091221120414.GD6309@redhat.com> <4B2F657B.1060603@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B2F657B.1060603@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Alexander Graf , Gleb Natapov , qemu-devel@nongnu.org On Mon, Dec 21, 2009 at 02:09:31PM +0200, Avi Kivity wrote: > On 12/21/2009 02:04 PM, Michael S. Tsirkin wrote: >> >> I think so - if this does not happen a lot, it's not a problem to phone home, >> right? >> > > I'm sure it's very annoying when it happens. It could well be less annoying than having your guest be slow every day because qemu masked CPU features that guest needs to be fast. At least with a CPU upgrade, casual user can easily disagnose the problem: the system was changed. If qemu is slow by default, there's no way to find out why without reading the manual. And we don't have one :) > -- > error compiling committee.c: too many arguments to function