From: Ross Boylan <ross@biostat.ucsf.edu>
To: Johannes Schlatow <johannes.schlatow@gmx.de>
Cc: ross@biostat.ucsf.edu, kvm@vger.kernel.org
Subject: Re: XP smp using a lot of CPU
Date: Thu, 14 May 2009 08:40:40 -0700 [thread overview]
Message-ID: <1242315640.27410.1.camel@corn.betterworld.us> (raw)
In-Reply-To: <fupb74dtcl3kru3oo7UYAxe124vaj_firegpg@mail.gmail.com>
On Thu, 2009-05-14 at 12:19 +0200, Johannes Schlatow wrote:
> I had a similar problem some weeks ago. Finally I found out that my VM
> running WinXP was working on a non-acpi system (maybe I started kvm
> with -no-acpi option during the installation). In the Device Manager
> there has to be the entry Computer->"ACPI Multiprocessor PC".
> Otherwise the VM produced 100% real cpu load on my machines (the fans
> were running on highest speed level).
> I just started the WinXP installation in repair mode and this did fix
> the problem.
>
> I hope this helps!
>
> regards
> Johannes
That may be it: I was running with -no-acpi. Various docs recommended
this for Windows performance, but your comment reminded me that acpi is
(I think) required for multiprocessors.
I'll be in where I can check on this later today.
Thanks.
Ross
>
> On Wed, May 13, 2009 at 2:41 AM, Ross Boylan <ross@biostat.ucsf.edu>
> wrote:
> I just installed XP into a new VM, specifying -smp 2 for the
> machine.
> According to top, it's using nearly 200% of a cpu even when
> I'm not
> doing anything.
>
> Is this real CPU useage, or just a reporting problem (just as
> my disk
> image is big according to ls, but isn't really)?
>
> If it's real, is there anything I can do about it?
>
> kvm 0.7.2 on Debian Lenny (but 2.6.29 kernel), amd64. Xeon
> chips; 32
> bit version of XP pro installed, now fully patched (including
> the
> Windows Genuine Advantage stuff, though I cancelled it when it
> wanted to
> run).
>
> Task manager in XP shows virtually no CPU useage.
>
> Please cc me on responses.
>
> Thanks for any assistance.
> --
> Ross Boylan wk: (415)
> 514-8146
> 185 Berry St #5700
> ross@biostat.ucsf.edu
> Dept of Epidemiology and Biostatistics fax: (415)
> 514-8150
> University of California, San Francisco
> San Francisco, CA 94107-1739 hm: (415)
> 550-1062
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
>
>
prev parent reply other threads:[~2009-05-14 15:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 0:41 XP smp using a lot of CPU Ross Boylan
2009-05-13 1:05 ` Elias Probst
2009-05-13 6:56 ` Avi Kivity
2009-05-14 14:10 ` Kevin Shanahan
2009-05-14 20:01 ` Ross Boylan
[not found] ` <20090515145651.GB6304@amt.cnet>
2009-05-15 15:41 ` Ross Boylan
2009-05-15 20:24 ` XP smp using a lot of CPU [SOLVED] Ross Boylan
2009-05-15 23:00 ` Brian Jackson
2009-05-13 20:23 ` XP smp using a lot of CPU Erik Rull
2009-05-17 21:35 ` Avi Kivity
2009-05-19 17:35 ` Erik Rull
2009-05-20 12:01 ` Avi Kivity
2009-05-20 20:00 ` Erik Rull
2009-05-24 11:42 ` Avi Kivity
2009-05-25 10:01 ` Erik Rull
2009-05-25 10:46 ` Avi Kivity
[not found] ` <fupb74dtcl3kru3oo7UYAxe124vaj_firegpg@mail.gmail.com>
2009-05-14 10:25 ` Johannes Schlatow
2009-05-14 15:40 ` Ross Boylan [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=1242315640.27410.1.camel@corn.betterworld.us \
--to=ross@biostat.ucsf.edu \
--cc=johannes.schlatow@gmx.de \
--cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox