From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39262) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vb8He-0001PO-0G for qemu-devel@nongnu.org; Tue, 29 Oct 2013 08:20:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vb8HX-00006n-Io for qemu-devel@nongnu.org; Tue, 29 Oct 2013 08:20:29 -0400 Received: from mx1.redhat.com ([209.132.183.28]:19989) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vb8HX-00006a-Aw for qemu-devel@nongnu.org; Tue, 29 Oct 2013 08:20:23 -0400 Date: Tue, 29 Oct 2013 14:20:11 +0200 From: Gleb Natapov Message-ID: <20131029122011.GE15657@redhat.com> References: <526F8457.5040907@kamp.de> <20131029111324.GA18289@redhat.com> <20131029112659.GB15657@redhat.com> <20131029121710.GC18289@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131029121710.GC18289@redhat.com> Subject: Re: [Qemu-devel] Prohibit Windows from running in QEMU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Peter Lieven , "qemu-devel@nongnu.org" On Tue, Oct 29, 2013 at 02:17:10PM +0200, Michael S. Tsirkin wrote: > On Tue, Oct 29, 2013 at 01:26:59PM +0200, Gleb Natapov wrote: > > On Tue, Oct 29, 2013 at 01:13:24PM +0200, Michael S. Tsirkin wrote: > > > On Tue, Oct 29, 2013 at 10:48:07AM +0100, Peter Lieven wrote: > > > > 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. > > > > > > > > Thanks, > > > > Peter > > > > > > - create a device > > > - write a linux driver > > > - if driver is not enabled crash guest > > > > > For how long to wait before a crash? > > Or don't crash, disable some other functionality, for example, you can > keep all network links down until your driver is loaded. > Unless your root is on nfs and driver is in a module :). Anyway if you need to write guest code there are easier ways to do it than writing new device/driver. In ideal world you could have used ACPI _OS(?) function, but since most bioses are broken for anything but Windows Linux reports that it is Windows too. -- Gleb.