From: Laszlo Ersek <lersek@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Prohibit Windows from running in QEMU
Date: Tue, 29 Oct 2013 15:12:26 +0100 [thread overview]
Message-ID: <526FC24A.1010106@redhat.com> (raw)
In-Reply-To: <526F92F4.8080406@kamp.de>
On 10/29/13 11:50, Peter Lieven wrote:
> On 29.10.2013 11:48, Paolo Bonzini wrote:
>> Il 29/10/2013 11:40, Peter Lieven ha scritto:
>>>> 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).
>> KVM_CPU_ID_SIGNATURE is 0x40000000.
>>
>>> Does this matter to Linux?
>> For recent versions it doesn't. Older versions will not be able to use
>> kvmclock (and other PV enhancements for KVM such as steal time or PV
>> EOI).
> Ok, so this is not an option today - maybe later...
>
> Any other idea to detect Windows is running or trying to start?
I don't know what I'm talking about. But:
- Maybe tracing MSR accesses could give you a "profile".
- Windows' ACPI parser is super cranky. You could pass in a custom (but
standardized) ACPI table on the command line (-acpitable) that only
triggers some warnings in Linux's port of ACPICA, but crashes Windows
(BSOD). Like, write & compile a simple table to AML, then mess it up
(eg. Package encoding or some such) with a hex editor. This would take
some experimentation as well, but searching existing bug reports could help.
Laszlo
next prev parent reply other threads:[~2013-10-29 14:10 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 [this message]
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
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=526FC24A.1010106@redhat.com \
--to=lersek@redhat.com \
--cc=pbonzini@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.