All of lore.kernel.org
 help / color / mirror / Atom feed
From: foure patrick <patrick.foure@dds.fr>
To: qemu-devel@nongnu.org
Cc: Serge Martins <serge.martins@dds.fr>
Subject: [Qemu-devel] QEMU CPU Overload on solaris10-x86
Date: Mon, 05 May 2008 13:01:06 +0200	[thread overview]
Message-ID: <481EE8F2.6000107@dds.fr> (raw)

Hi all ,

I have a strange behavior of qemu on solaris10-x86 update4 :
on a AMD platform ( sun x2100 ) : no problem
on a Xeon platform ( sun x4150 ) : the cpu is allways at 100% used 
exclusively by qemu process ( LWP nb 1 )
The guest OS is XP SP2 and the windows cpu is idle .

The release of solaris is : sol10-x86 update4 (5.10 Generic_120012-14)
and the release of qemu is : 0.8.2__cvs20070120sat
Same windows XP image .

We have tried to rebuild QEMU 0.9.0 binaries on the Xeon platform with 
GCC -3.4.2 but the same problem appear.

Does someone have any idea why i have a different behavior between the 2 
processors ?

Thanks by advance for any help
Patrick Foure

                 reply	other threads:[~2008-05-05 11:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=481EE8F2.6000107@dds.fr \
    --to=patrick.foure@dds.fr \
    --cc=qemu-devel@nongnu.org \
    --cc=serge.martins@dds.fr \
    /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.