From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: WinXP virtual crashes on 0.12.1.2 but not 0.12.1.1 Date: Mon, 25 Jan 2010 18:22:00 +0200 Message-ID: <4B5DC528.40000@redhat.com> References: <4B43643F.8090303@siriusit.co.uk> <4B4373A8.8050807@redhat.com> <4B44731A.4020405@siriusit.co.uk> <4B448513.6070505@redhat.com> <4B448715.9000602@siriusit.co.uk> <4B4489F5.4000409@redhat.com> <4B44B018.90003@siriusit.co.uk> <4B45A05A.5020304@redhat.com> <4B45AFA1.6090008@siriusit.co.uk> <4B5BF98A.5040408@redhat.com> <4B5DB5A8.4000108@siriusit.co.uk> <4B5DB86F.202@redhat.com> <4B5DC16F.9020909@siriusit.co.uk> <4B5DC233.2090407@redhat.com> <4B5DC471.8040500@siriusit.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Mark Cave-Ayland Return-path: Received: from mx1.redhat.com ([209.132.183.28]:56836 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751385Ab0AYQWJ (ORCPT ); Mon, 25 Jan 2010 11:22:09 -0500 In-Reply-To: <4B5DC471.8040500@siriusit.co.uk> Sender: kvm-owner@vger.kernel.org List-ID: On 01/25/2010 06:18 PM, Mark Cave-Ayland wrote: > Avi Kivity wrote: > >>> I've had a quick look at this, and I can't work out how to enable >>> kvm trace in Kconfig. Is there any documentation on how to build >>> with kvm trace enabled for debugging? >> >> CONFIG_FTRACE, CONFIG_TRACEPOINTS should be sufficient, I think. >> 2.6.32 or later IIRC. > > Hmmm these already look as if they have been enabled. Does the output > go to syslog or does it appear on a device somewhere in /proc? > echo kvm > /sys/kernel/debug/tracing/set_event (you can also enable just the msr and cpuid events, see /sys/kernel/debug/tracing/events) cat /sys/kernel/debug/trace -- error compiling committee.c: too many arguments to function