From: Gleb Natapov <gleb@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Peter Lieven <pl@kamp.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Prohibit Windows from running in QEMU
Date: Tue, 29 Oct 2013 14:20:11 +0200 [thread overview]
Message-ID: <20131029122011.GE15657@redhat.com> (raw)
In-Reply-To: <20131029121710.GC18289@redhat.com>
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.
next prev parent reply other threads:[~2013-10-29 12:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 9:48 [Qemu-devel] Prohibit Windows from running in QEMU Peter Lieven
2013-10-29 9:59 ` Paolo Bonzini
2013-10-29 10:11 ` Peter Lieven
2013-10-29 10:19 ` Paolo Bonzini
2013-10-29 10:25 ` Gleb Natapov
2013-10-29 10:40 ` Peter Lieven
2013-10-29 10:48 ` Paolo Bonzini
2013-10-29 10:50 ` Peter Lieven
2013-10-29 14:12 ` Laszlo Ersek
2013-10-29 15:55 ` BALATON Zoltan
2013-10-29 16:00 ` Paolo Bonzini
2013-10-29 16:29 ` Peter Lieven
2017-08-04 9:58 ` Peter Lieven
2017-08-04 10:23 ` Paolo Bonzini
2017-08-04 10:27 ` Peter Lieven
2017-08-04 10:43 ` Paolo Bonzini
2017-08-04 10:44 ` Peter Lieven
2013-10-29 11:13 ` Michael S. Tsirkin
2013-10-29 11:26 ` Gleb Natapov
2013-10-29 11:31 ` Peter Lieven
2013-10-29 11:34 ` Gleb Natapov
2013-10-29 12:17 ` Michael S. Tsirkin
2013-10-29 12:20 ` Gleb Natapov [this message]
2013-10-30 0:16 ` Li Guang
2013-10-29 11:47 ` Daniel P. Berrange
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131029122011.GE15657@redhat.com \
--to=gleb@redhat.com \
--cc=mst@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.