From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MJ4Dq-0006tn-DQ for qemu-devel@nongnu.org; Tue, 23 Jun 2009 07:31:30 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MJ4Dl-0006q1-40 for qemu-devel@nongnu.org; Tue, 23 Jun 2009 07:31:29 -0400 Received: from [199.232.76.173] (port=55934 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJ4Dk-0006pD-U8 for qemu-devel@nongnu.org; Tue, 23 Jun 2009 07:31:24 -0400 Received: from mx20.gnu.org ([199.232.41.8]:4393) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MJ4Dk-0004hn-1r for qemu-devel@nongnu.org; Tue, 23 Jun 2009 07:31:24 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MJ4Di-0008Fi-KQ for qemu-devel@nongnu.org; Tue, 23 Jun 2009 07:31:22 -0400 From: Paul Brook Subject: Re: [Qemu-devel] Re: [PATCH 1/2] allow hypervisor CPUID bit to be overriden Date: Tue, 23 Jun 2009 12:31:12 +0100 References: <1245707244-743-1-git-send-email-andre.przywara@amd.com> <4A40A7EC.8070100@redhat.com> In-Reply-To: <4A40A7EC.8070100@redhat.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200906231231.15206.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Andre Przywara , aliguori@us.ibm.com, Avi Kivity , kvm@vger.kernel.org On Tuesday 23 June 2009, Avi Kivity wrote: > On 06/23/2009 12:47 AM, Andre Przywara wrote: > > KVM defaults to the hypervisor CPUID bit to be set, whereas pure QEMU > > clears it. On some occasions one want to set or clear it the other way > > round (for instance to get HyperV running inside a guest). > > Allow the default to be overridden on the command line and fix some > > whitespace damage on the way. > > It makes sense for qemu to set the hypervisor bit unconditionally. A > guest running under qemu is not bare metal. I see no reason why a guest has to be told that it's running inside a VM. In principle an appropriately configured qemu should be indistinguishable from real hardware. In practice it's technically infeasible to cover absolutely everything, but if we set this bit we're not even trying. I have no objection to the bit being set by default for the QEMU CPU types. Paul