From: Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Gildas <gildas.ml-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: exposed processor type, unsupported operations, intelppm.sys and windows crashs
Date: Thu, 20 Sep 2007 07:07:28 +0200 [thread overview]
Message-ID: <46F20010.60107@qumranet.com> (raw)
In-Reply-To: <b2ace7f20709200840w547630b3oc8d0a299b8a592dc-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Gildas wrote:
> Hi,
>
> I had a problem when moving my windows XP machine from the ACPI HAL to
> the standard PC HAL in order to get better performances (as pointed in
> http://kvm.qumranet.com/kvmwiki/Windows_ACPI_Workaround): on reboot
> the machine would just BSOD with kvm but work with -no-kvm.
>
> The BSOD message was about intelppm.sys, so I did my homework,
> searched on Google and I found a page on Ben Armstrong's Blog:
> http://blogs.msdn.com/virtual_pc_guy/archive/2005/10/24/484461.aspx
>
> The very interesting part of the article is:
>
> "In the mean time we have made some subtle changes to the way our
> hardware exposes the processor in Virtual Server R2 so that in future
> products these drivers should never get loaded inside of virtual
> machines."
>
> Should similar tricks be performed in kvm?
>
kvm have patch that we wrote that let us play with how the cpu expose
itself by the meaning of the cpuid instruction.
but i believe it is something else ther.e
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
prev parent reply other threads:[~2007-09-20 5:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 15:40 exposed processor type, unsupported operations, intelppm.sys and windows crashs Gildas
[not found] ` <b2ace7f20709200840w547630b3oc8d0a299b8a592dc-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-20 5:07 ` Izik Eidus [this message]
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=46F20010.60107@qumranet.com \
--to=izike-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=gildas.ml-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.