From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: performance trouble Date: Mon, 30 Jan 2012 19:21:20 +0200 Message-ID: <4F26D190.4040207@redhat.com> References: <20120123082837.GC26955@nfs-rbx.ovh.net> <20120130153655.GI26955@nfs-rbx.ovh.net> <201201301020.35161.iggy@theiggy.com> <20120130165140.GJ26955@nfs-rbx.ovh.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: David Cure Return-path: Received: from mx1.redhat.com ([209.132.183.28]:20062 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752132Ab2A3RV0 (ORCPT ); Mon, 30 Jan 2012 12:21:26 -0500 In-Reply-To: <20120130165140.GJ26955@nfs-rbx.ovh.net> Sender: kvm-owner@vger.kernel.org List-ID: 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