From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: WinXP virtual crashes on 0.12.1.2 but not 0.12.1.1
Date: Tue, 26 Jan 2010 08:18:18 +0200
Message-ID: <4B5E892A.1090508@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> <4B5DC528.40000@redhat.com> <4B5DCCD9.7040709@siriusit.co.uk> <4B5DD6E2.7010306@redhat.com> <4B5E1A6D.1050109@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 <mark.cave-ayland@siriusit.co.uk>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:38291 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751865Ab0AZGSZ (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 26 Jan 2010 01:18:25 -0500
In-Reply-To: <4B5E1A6D.1050109@siriusit.co.uk>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 01/26/2010 12:25 AM, Mark Cave-Ayland wrote:
> Avi Kivity wrote:
>
>> Unfortunately msr tracing fails to record some important 
>> information.  I just posted a patch to fix this.  Can you rerun from 
>> kvm.git branch msr-trace?  That contains the fix.
>
> Done.
>
> http://pastebin.com/m209b1f13
>
> Hopefully this trace should give a better indication of when the 
> problem occurs since I also found the <on_reboot> option in libvirt - 
> hence on this trace the VM shuts down immediately instead of rebooting 
> like the earlier trace.
>
>

Unfortunately, no such luck.  Apparently this is not msr/cpuid related - 
perhaps power management.  Can you enable the kvm_mmio and kvm_pio 
events?  Perhaps they will provide a clue.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.