From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:35959)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1Vb6Ue-0001hf-Gu
	for qemu-devel@nongnu.org; Tue, 29 Oct 2013 06:25:54 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1Vb6UY-0005dz-Hf
	for qemu-devel@nongnu.org; Tue, 29 Oct 2013 06:25:48 -0400
Received: from mx1.redhat.com ([209.132.183.28]:26811)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <gleb@redhat.com>) id 1Vb6UY-0005dt-9Y
	for qemu-devel@nongnu.org; Tue, 29 Oct 2013 06:25:42 -0400
Date: Tue, 29 Oct 2013 12:25:33 +0200
From: Gleb Natapov <gleb@redhat.com>
Message-ID: <20131029102533.GY15657@redhat.com>
References: <526F8457.5040907@kamp.de> <526F8701.2030906@redhat.com>
	<526F89B4.5080504@kamp.de> <526F8BCA.7090503@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <526F8BCA.7090503@redhat.com>
Subject: Re: [Qemu-devel] Prohibit Windows from running in QEMU
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Lieven <pl@kamp.de>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

On Tue, Oct 29, 2013 at 11:19:54AM +0100, Paolo Bonzini wrote:
> Il 29/10/2013 11:11, Peter Lieven ha scritto:
> > On 29.10.2013 10:59, Paolo Bonzini wrote:
> >> Il 29/10/2013 10:48, Peter Lieven ha scritto:
> >>> Hi all,
> >>>
> >>> this question might seem a bit weird, but does anyone see a good way to
> >>> avoid
> >>> that Windows is able to boot inside qemu?
> >>>
> >>> We have defined several profiles for different operation systems and
> >>> I want
> >>> to avoid that someone chooses Linux and then installs Windows within
> >>> a VM. Reason is licensing.
> >> Patch QEMU to crash when Hyper-V extensions are enabled...
> > 
> > I was thinking about this, but wouldn't this mean the cpu signature
> > would always be "Microsoft Hv"
> > and not "KVMKVMKVM\0\0\0"?
> 
> The KVM signature should be at CPUID leaf 0x40000100.
> 
But only recently Linux started to search for it there.

--
			Gleb.