From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MJhSn-0007mq-SA for qemu-devel@nongnu.org; Thu, 25 Jun 2009 01:25:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MJhSi-0007mN-Cy for qemu-devel@nongnu.org; Thu, 25 Jun 2009 01:25:32 -0400 Received: from [199.232.76.173] (port=55319 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJhSi-0007mK-3t for qemu-devel@nongnu.org; Thu, 25 Jun 2009 01:25:28 -0400 Received: from mx2.redhat.com ([66.187.237.31]:40544) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MJhSh-0006LI-NS for qemu-devel@nongnu.org; Thu, 25 Jun 2009 01:25:27 -0400 Date: Thu, 25 Jun 2009 08:23:21 +0300 From: Gleb Natapov Subject: Re: [Qemu-devel] Re: [PATCH 1/2] allow hypervisor CPUID bit to be overriden Message-ID: <20090625052321.GJ20289@redhat.com> References: <1245707244-743-1-git-send-email-andre.przywara@amd.com> <4A40A7EC.8070100@redhat.com> <200906231231.15206.paul@codesourcery.com> <4A40BE07.5080906@redhat.com> <20090624212041.GB14121@shareable.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090624212041.GB14121@shareable.org> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jamie Lokier Cc: Andre Przywara , aliguori@us.ibm.com, kvm@vger.kernel.org, qemu-devel@nongnu.org, Avi Kivity , Paul Brook On Wed, Jun 24, 2009 at 10:20:41PM +0100, Jamie Lokier wrote: > Avi Kivity wrote: > > On 06/23/2009 02:31 PM, Paul Brook wrote: > > >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. > > > > > > > I agree it's pointless, but it is a Microsoft requirement for passing > > their SVVP tests. Enabling it by default makes life a little easier for > > users who wish to validate their hypervisor and has no drawbacks. > > Hold on. > > Do the SVVP tests fail on a real (non-virtal) machine then? > SVVP -> Server Virtualization Validation Program Definitely fails on a real machine :) -- Gleb.