All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: KVM list <kvm@vger.kernel.org>, nikola.ciprich@linuxbox.cz
Subject: Re: qemu-kvm-0.13.0 - winsows 2008 - chkdisk too slow
Date: Thu, 06 Jan 2011 11:30:19 +0200	[thread overview]
Message-ID: <4D258BAB.1020004@redhat.com> (raw)
In-Reply-To: <4D258B18.5000402@redhat.com>

On 01/06/2011 11:27 AM, Avi Kivity wrote:
> On 01/06/2011 11:20 AM, Nikola Ciprich wrote:
>> Hello Avi!
>> On Thu, Jan 06, 2011 at 11:08:32AM +0200, Avi Kivity wrote:
>> >  Let's start with a few 'kvm_stat -1' snapshots while this is going 
>> on.
>>
>> here it is, but note that there are few more machines running on this 
>> host.
>> but they're almost idle in contrast to this windows one, so I hope 
>> it's not problem.
>
>> kvm_cr                       780       772
>> kvm_emulate_insn           46181     44982
>> kvm_entry                  55012     53867
>> kvm_exit                   55182     53884
>
> It's emulating quite a bit.  Let's see why.
>
> - install udis86 and udis86-devel
> - build and install 
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
> - run trace-cmd record -e kvm -b 100000 -P pid1 -P pid2, ctrl-C after 
> a few seconds (pid1/pid2 are thread ids from 'info cpus' of the bad 
> guest, plus the pid of the qemu process itself)
> - post the resulting trace.dat somewhere
>

btw, that 100000 is 400MB of nonswappable kernel memory per cpu, so if 
you have lots of cpus and not enough memory, adjust it down.

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


  reply	other threads:[~2011-01-06  9:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06  7:48 qemu-kvm-0.13.0 - winsows 2008 - chkdisk too slow Nikola Ciprich
2011-01-06  9:03 ` Stefan Hajnoczi
2011-01-06  9:06   ` Nikola Ciprich
2011-01-06  9:08 ` Avi Kivity
2011-01-06  9:20   ` Nikola Ciprich
2011-01-06  9:27     ` Avi Kivity
2011-01-06  9:30       ` Avi Kivity [this message]
2011-01-06  9:42       ` Nikola Ciprich
2011-01-06 10:19         ` Avi Kivity
2011-01-06 10:25           ` Nikola Ciprich
2011-01-06 10:50             ` Avi Kivity
2011-01-06 11:06           ` Daniel P. Berrange
2011-01-06 12:19             ` Nikola Ciprich
2011-01-06 12:18           ` Nikola Ciprich
2011-01-06 13:26             ` Avi Kivity
2011-01-06 13:55               ` Nikola Ciprich
2011-01-06 14:37                 ` Avi Kivity
2011-01-06 15:38                   ` Nikola Ciprich
2011-01-09 12:36                     ` Nikola Ciprich
2011-01-09 12:39                       ` Avi Kivity
2011-01-09 13:36                         ` Nikola Ciprich
2011-01-09 13:44                           ` Nikola Ciprich
2011-01-09 14:13                             ` Avi Kivity
2011-01-09 14:13                           ` Avi Kivity
2011-01-09 14:27                             ` Nikola Ciprich
2011-01-09 14:36                               ` Avi Kivity
2011-01-09 15:15                                 ` Nikola Ciprich
2011-01-09 20:10                                   ` Nikola Ciprich
2011-01-10  9:23                                     ` Avi Kivity

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=4D258BAB.1020004@redhat.com \
    --to=avi@redhat.com \
    --cc=extmaillist@linuxbox.cz \
    --cc=kvm@vger.kernel.org \
    --cc=nikola.ciprich@linuxbox.cz \
    /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.