From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:39509)
	by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <pl@kamp.de>)
	id 1Vb6is-0005BW-Md
	for qemu-devel@nongnu.org; Tue, 29 Oct 2013 06:40:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pl@kamp.de>) id 1Vb6ij-0001nA-R3
	for qemu-devel@nongnu.org; Tue, 29 Oct 2013 06:40:30 -0400
Received: from mx.ipv6.kamp.de ([2a02:248:0:51::16]:34993 helo=mx01.kamp.de)
	by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <pl@kamp.de>)
	id 1Vb6ij-0001mn-FR
	for qemu-devel@nongnu.org; Tue, 29 Oct 2013 06:40:21 -0400
Message-ID: <526F909A.8000004@kamp.de>
Date: Tue, 29 Oct 2013 11:40:26 +0100
From: Peter Lieven <pl@kamp.de>
MIME-Version: 1.0
References: <526F8457.5040907@kamp.de> <526F8701.2030906@redhat.com>
	<526F89B4.5080504@kamp.de> <526F8BCA.7090503@redhat.com>
In-Reply-To: <526F8BCA.7090503@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

On 29.10.2013 11:19, 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.
If I enable hyperv for all vServers the signature is at KVM_CPUID_SIGNATURE_NEXT (0x40000100) otherwise
at KVM_CPUID_SIGNATURE (0x0). Does this matter to Linux?

Peter