public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ross Boylan <ross@biostat.ucsf.edu>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: ross@biostat.ucsf.edu, Kevin Shanahan <kmshanah@ucwb.org.au>,
	Avi Kivity <avi@redhat.com>,
	kvm@vger.kernel.org
Subject: Re: XP smp using a lot of CPU [SOLVED]
Date: Fri, 15 May 2009 13:24:21 -0700	[thread overview]
Message-ID: <1242419061.2852.6.camel@iron.psg.net> (raw)
In-Reply-To: <1242402117.17637.14.camel@corn.betterworld.us>

Using ACPI fixes the problem; CPU useage is now quite low.  Start line
was
sudo vdeq kvm -net nic,vlan=1,macaddr=52:54:a0:12:01:00 \
    -net vde,vlan=1,sock=/var/run/vde2/tap0.ctl \
    -boot d -cdrom /usr/local/backup/XPProSP3.iso \
    -std-vga -hda /dev/turtle/XP00 \
    -soundhw es1370 -localtime -m 1G -smp 2
I switched to -boot c later.

I ended up doing a fresh install; my repair got mucked up and I got the
message "The requested lookup key was not found in any active activation
context" when I entered a location into MSIE, including when I tried to
run Windows Update.  Googling showed this might indicate some permission
or file corruption issues.  They may have happened during my earlier
(virtual) system hang.

My experience suggests a theory: if you use SMP with XP (i.e., more than
1 virtual processor) you should enable acpi, i.e., not say -no-acpi.  It
this is true, the advice to run windows with -no-acpi should probably be
updated.  It's possible single CPU systems are affected as well.

Ross


  reply	other threads:[~2009-05-15 20:24 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         ` Ross Boylan [this message]
2009-05-15 23:00           ` XP smp using a lot of CPU [SOLVED] 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

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=1242419061.2852.6.camel@iron.psg.net \
    --to=ross@biostat.ucsf.edu \
    --cc=avi@redhat.com \
    --cc=kmshanah@ucwb.org.au \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /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