From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Network throughput limits for local VM <-> VM communication Date: Thu, 18 Jun 2009 11:37:38 +0300 Message-ID: <4A39FCD2.6080507@redhat.com> References: <0199E0D51A61344794750DC57738F58E67D2398F9E@GVW1118EXC.americas.hpqcorp.net> <200906101529.47103.arnd@arndb.de> <0199E0D51A61344794750DC57738F58E67D2399710@GVW1118EXC.americas.hpqcorp.net> <200906110949.16197.arnd@arndb.de> <0199E0D51A61344794750DC57738F58E67D23998F5@GVW1118EXC.americas.hpqcorp.net> <4A30BD98.6040302@redhat.com> <0199E0D51A61344794750DC57738F58E67D2399972@GVW1118EXC.americas.hpqcorp.net> <4A30C566.7040109@redhat.com> <0199E0D51A61344794750DC57738F58E67D2DCF44F@GVW1118EXC.americas.hpqcorp.net> <4A38A03B.20904@redhat.com> <0199E0D51A61344794750DC57738F58E67D2DCF4BF@GVW1118EXC.americas.hpqcorp.net> <4A38E00A.5090402@redhat.com> <0199E0D51A61344794750DC57738F58E67D301B624@GVW1118EXC.americas.hpqcorp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Arnd Bergmann , Mark McLoughlin , "kvm@vger.kernel.org" To: "Fischer, Anna" Return-path: Received: from mx2.redhat.com ([66.187.237.31]:44429 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752410AbZFRIhS (ORCPT ); Thu, 18 Jun 2009 04:37:18 -0400 In-Reply-To: <0199E0D51A61344794750DC57738F58E67D301B624@GVW1118EXC.americas.hpqcorp.net> Sender: kvm-owner@vger.kernel.org List-ID: On 06/17/2009 06:41 PM, Fischer, Anna wrote: > It still does not answer my question on why I only see low CPU utilization numbers with the e1000 virtual device model. There is no network stalling or packet drops or any other obvious issues when running with that model, but I am still seeing low CPU utilization numbers. What is preventing KVM here to use more of the host CPU capacity when the host is not doing anything else but run virtual machines? Is there any way that I can get higher CPU utilization out of KVM? > A missing wakeup might cause this, but I really have no idea how we can trace the cause. -- error compiling committee.c: too many arguments to function