On 01/30/2012 06:51 PM, David Cure wrote: > Le Mon, Jan 30, 2012 at 10:20:34AM -0600, Brian Jackson ecrivait : > > > > Without more info or some way to reproduce the problem, it would be pointless > > for one of the devs to spend much time on it. > > yes for sure. > > But I mean there is some way to trace at the KVM level what happens when the > program runs in the VM ? And perhaps with these infos some one see the > problem ;) (because with the upgrade of KVM/qemu we already cut the > response time by 2). > Start with top and vmstat to see if the cpu or I/O are the bottleneck (also helpful to run the Windows performance monitor in the guest). If it's the cpu, run kvm_stat and report its output. -- 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
