From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NMiZs-0000s4-LT for qemu-devel@nongnu.org; Mon, 21 Dec 2009 08:45:36 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NMiZn-0000qW-Eo for qemu-devel@nongnu.org; Mon, 21 Dec 2009 08:45:35 -0500 Received: from [199.232.76.173] (port=38006 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NMiZn-0000qT-Aa for qemu-devel@nongnu.org; Mon, 21 Dec 2009 08:45:31 -0500 Received: from ams-iport-2.cisco.com ([144.254.224.141]:17731) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.60) (envelope-from ) id 1NMiZl-0000EX-Qb for qemu-devel@nongnu.org; Mon, 21 Dec 2009 08:45:30 -0500 Message-ID: <4B2F7BF2.5090206@cisco.com> Date: Mon, 21 Dec 2009 06:45:22 -0700 From: "David S. Ahern" MIME-Version: 1.0 Subject: Re: [Qemu-devel] cpuid problem in upstream qemu with kvm References: <4B269D99.8080404@codemonkey.ws> <4B2DF334.6030208@redhat.com> <20091220155101.GB31257@redhat.com> <4B2E49E5.6050709@redhat.com> <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> In-Reply-To: <4B2F64A1.9050905@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity , Alexander Graf Cc: qemu-devel@nongnu.org, Gleb Natapov , "Michael S.Tsirkin" 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