From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Q: Stopped VM still using host cpu CPU ? Date: Sun, 18 Oct 2009 15:59:06 +0900 Message-ID: <4ADABCBA.8020004@redhat.com> References: <4AC8B6D9.7070003@redhat.com> <4AC8C018.6050302@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]:43525 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751610AbZJRG7L (ORCPT ); Sun, 18 Oct 2009 02:59:11 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 10/17/2009 06:35 AM, Daniel Schwager wrote: > > I'm not that familiar with oprofile ... > > so, setup with > opcontrol --deinit; modprobe oprofile timer=1; opcontrol --start > > gave me the following result: > > kvm03:~# opreport > Use 'opreport -l'. Make sure your qemu isn't stripped. > Try to start without timer=1 hung up my physical machine after daemon is > started: > kvm03:/opt/kvm-86-vnc-patch# opcontrol --deinit; modprobe oprofile ; > opcontrol --start > Stopping profiling. > Killing daemon. > Unloading oprofile module > Using default event: CPU_CLK_UNHALTED:100000:0:1:1 > Using 2.6+ OProfile kernel interface. > Using log file /var/lib/oprofile/samples/oprofiled.log > Daemon started. > > > Could I give you more information ? Should I setup oprofile in another > way ? > > Is there an oops in dmesg, or is the machine dead? What's the host kernel version? -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.