From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Cure Subject: Re: performance trouble Date: Thu, 22 Mar 2012 09:33:57 +0100 Message-ID: <20120322083357.GX12293@nfs-rbx.ovh.net> References: <20120223083807.GA17505@redhat.com> <20120316101331.GM12293@nfs-rbx.ovh.net> <20120319105134.GA27928@redhat.com> <20120320093220.GS12293@nfs-rbx.ovh.net> <20120320094541.GH22368@redhat.com> <20120320111839.GT12293@nfs-rbx.ovh.net> <20120320123821.GL22368@redhat.com> <20120321111001.GV12293@nfs-rbx.ovh.net> <4F6A1056.1020904@dlh.net> <20120322075345.GA22368@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Peter Lieven , Avi Kivity , kvm@vger.kernel.org, Vadim Rozenfeld To: Gleb Natapov Return-path: Received: from gandalf.cure.nom.fr ([91.121.137.146]:52817 "EHLO gandalf.cure.nom.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932191Ab2CVIeB (ORCPT ); Thu, 22 Mar 2012 04:34:01 -0400 Content-Disposition: inline In-Reply-To: <20120322075345.GA22368@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Le Thu, Mar 22, 2012 at 09:53:45AM +0200, Gleb Natapov ecrivait : > > All true. I asked to try -hypervisor only to verify where we loose > performance. Since you get good result with it frequent access to PM > timer is probably the reason. I do not recommend using -hypervisor for > production! so if I leave cpu as previous (not defined) and only disable hpet and use 1 vcpu, it's ok for production ? Is there a workaround for this PM access ? David.