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
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
