From: Paolo Bonzini <pbonzini@redhat.com>
To: Brian Rak <brak@gameservers.com>
Cc: kvm@vger.kernel.org
Subject: Re: Windows Server 2008R2 KVM guest performance issues
Date: Tue, 27 Aug 2013 09:18:00 +0200 [thread overview]
Message-ID: <521C52A8.40801@redhat.com> (raw)
In-Reply-To: <521BA934.3050507@gameservers.com>
Il 26/08/2013 21:15, Brian Rak ha scritto:
>
> Samples: 62M of event 'cycles', Event count (approx.): 642019289177
> 64.69% [kernel] [k] _raw_spin_lock
> 2.59% qemu-system-x86_64 [.] 0x00000000001e688d
> 1.90% [kernel] [k] native_write_msr_safe
> 0.84% [kvm] [k] vcpu_enter_guest
> 0.80% [kernel] [k] __schedule
> 0.77% [kvm_intel] [k] vmx_vcpu_run
> 0.68% [kernel] [k] effective_load
> 0.65% [kernel] [k] update_cfs_shares
> 0.62% [kernel] [k] _raw_spin_lock_irq
> 0.61% [kernel] [k] native_read_msr_safe
> 0.56% [kernel] [k] enqueue_entity
Can you capture the call graphs, too (perf record -g)?
> I've captured 20,000 lines of kvm trace output. This can be found
> https://gist.github.com/devicenull/fa8f49d4366060029ee4/raw/fb89720d34b43920be22e3e9a1d88962bf305da8/trace
The guest is doing quite a lot of exits per second, mostly to (a) access
the ACPI timer (b) service NMIs. In fact, every NMI is reading the
timer too and causing an exit to QEMU.
So it is also possible that you have to debug this inside the guest, to
see if these exits are expected or not.
Paolo
next prev parent reply other threads:[~2013-08-27 7:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 19:15 Windows Server 2008R2 KVM guest performance issues Brian Rak
2013-08-26 22:01 ` Brian Rak
2013-08-27 7:18 ` Paolo Bonzini [this message]
2013-08-27 7:38 ` Gleb Natapov
2013-08-27 8:38 ` Paolo Bonzini
2013-08-27 8:44 ` Gleb Natapov
2013-08-27 14:09 ` Brian Rak
2013-08-27 14:44 ` Brian Rak
2013-08-27 15:09 ` Paolo Bonzini
2013-08-27 16:45 ` Brian Rak
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=521C52A8.40801@redhat.com \
--to=pbonzini@redhat.com \
--cc=brak@gameservers.com \
--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 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.