kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Thomas Beinicke <thomas.beinicke@fsd-web.de>
Cc: KVM mailing list <kvm@vger.kernel.org>
Subject: Re: High CPU load on target host after migration
Date: Thu, 06 May 2010 12:23:20 +0300	[thread overview]
Message-ID: <4BE28A88.7020805@redhat.com> (raw)
In-Reply-To: <201004282314.41209.thomas.beinicke@fsd-web.de>

On 04/29/2010 12:14 AM, Thomas Beinicke wrote:
> Hi,
>
> I have been toying around with kvm / libvirt / virt-manager and it's migration
> feature.
> Both host machines are running a 2.6.33 Kernel.
>
> One host is a Dual Quad Core Intel Xeon E5520  @ 2.27GHz and the other is a
> Dual Quad Core Intel E5420  @ 2.50GHz.
>
> Migrating Linux machines works great but Windows XP SP3 is giving me a
> headache.
> The migration process finishes without any crash/error but the CPU load on the
> target host is ~50% on two cores. There is no CPU intensive task running
> inside the VM though.
> "Removing" the network card from the VM and migrating it between the two
> machines doesn't seem to trigger the high CPU load.
> As network driver I tried the realtek and Red Hat virtio driver but it doesn't
> seem to make a difference.
>
> Any insights on what could cause this situation and how to best debug it?
>
>    

Can you run a profiler and see where qemu (or kvm) is spending its time?

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-05-06  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 21:14 High CPU load on target host after migration Thomas Beinicke
2010-05-06  9:23 ` Avi Kivity [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-04-30 21:19 Thomas Beinicke

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=4BE28A88.7020805@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=thomas.beinicke@fsd-web.de \
    /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;
as well as URLs for NNTP newsgroup(s).