From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NMiiU-0008SI-JV for qemu-devel@nongnu.org; Mon, 21 Dec 2009 08:54:30 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NMiiQ-0008Qz-RJ for qemu-devel@nongnu.org; Mon, 21 Dec 2009 08:54:30 -0500 Received: from [199.232.76.173] (port=34149 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NMiiQ-0008Qr-Ny for qemu-devel@nongnu.org; Mon, 21 Dec 2009 08:54:26 -0500 Received: from mx1.redhat.com ([209.132.183.28]:64137) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NMiiQ-00027V-Ao for qemu-devel@nongnu.org; Mon, 21 Dec 2009 08:54:26 -0500 Date: Mon, 21 Dec 2009 15:51:14 +0200 From: "Michael S. Tsirkin" Subject: Re: [Qemu-devel] cpuid problem in upstream qemu with kvm Message-ID: <20091221135114.GA7956@redhat.com> References: <20091220165612.GC31257@redhat.com> <20091220171822.GD31257@redhat.com> <4B2F581A.7030206@redhat.com> <20091221111856.GA6309@redhat.com> <0B948C77-7A15-4321-BA7C-059AA5FC3019@suse.de> <20091221113852.GB6309@redhat.com> <7AE7527C-B437-4807-8F26-515452C789AD@suse.de> <4B2F64A1.9050905@redhat.com> <4B2F7BF2.5090206@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B2F7BF2.5090206@cisco.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "David S. Ahern" Cc: qemu-devel@nongnu.org, Avi Kivity , Gleb Natapov , Alexander Graf On Mon, Dec 21, 2009 at 06:45:22AM -0700, David S. Ahern wrote: > > On 12/21/2009 05:05 AM, Avi Kivity wrote: > > On 12/21/2009 01:45 PM, Alexander Graf wrote: > >> > >> Well, we have two groups: > >> > >> 1) Casual user w/o management app > >> 2) Enterprise user w/ management app > >> > >> So I clearly belong to the first group. > >> > > > > 3) Developer/power user who knows what he's about. > > > > You could simply add -cpu qemu64 for those guests that care about it. > > > > 4) embedded virtualization where the use of a management app provides > little to no added benefit and everything has to be > "automated" (ie., no user). > > My point is there are other use cases besides data center deployments > (aka enterprise) and workstation (casual/power user). There are use > cases where virtualization is just yet another tool to achieve a product. > > David Yes, but unless someone runs qemu directly, default value for any flag does not matter much. -- MST