From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Q: Stopped VM still using host cpu CPU ? Date: Thu, 22 Oct 2009 15:29:02 +0200 Message-ID: <4AE05E1E.3050308@redhat.com> References: <4AC8B6D9.7070003@redhat.com> <4AC8C018.6050302@redhat.com> <4ADABCBA.8020004@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Daniel Schwager Return-path: Received: from mx1.redhat.com ([209.132.183.28]:1480 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754812AbZJVN3F (ORCPT ); Thu, 22 Oct 2009 09:29:05 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 10/21/2009 10:29 PM, Daniel Schwager wrote: > > **** opreport -l --symbols | less > CPU: CPU with timer interrupt, speed 0 MHz (estimated) > Profiling through timer interrupt > samples % image name app name > symbol name > 418814 98.5250 no-vmlinux no-vmlinux (no > symbols) > 1228 0.2889 qemu-system-x86_64 qemu-system-x86_64 > main_loop_wait > 888 0.2089 libpthread-2.8.so libpthread-2.8.so > __read_nocancel > ... > > Sorry, I gave you the wrong instructions. Since most of the time is spent in vmlinux, we want to trace vmlinux, not qemu. Three ways to see what is happening: - set up vmlinux (you'll need to install the correct kernel-debuginfo package to get this). - strace -p `pgrep qemu` and see what syscalls take place - run 'top' and look at the wchan field ('f' 'y' will show it if it is hidden) Probably easiest in reverse order as listed. -- error compiling committee.c: too many arguments to function