From mboxrd@z Thu Jan  1 00:00:00 1970
From: Danny ter Haar <dth@dth.net>
Subject: Re: kvm problems on new hardware
Date: Fri, 30 Oct 2009 09:54:11 +0100
Message-ID: <1256892851.15399.17.camel@thinkpaddth>
References: <20091026100651.GA15566@dth.net> <4AE6C126.5030803@redhat.com>
	 <1256639276.3889.29.camel@thinkpaddth> <4AE6CCA1.9000307@redhat.com>
	 <1256841444.4117.16.camel@thinkpaddth> <20091029220740.GI13808@us.ibm.com>
	 <4AEA9F79.4070607@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: Ryan Harper <ryanh@us.ibm.com>, Avi Kivity <avi@redhat.com>,
	kvm@vger.kernel.org
To: Chris Lalancette <clalance@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from zaphod.dth.net ([85.159.112.68]:60573 "EHLO zaphod.dth.net"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1755491AbZJ3IyM (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 30 Oct 2009 04:54:12 -0400
In-Reply-To: <4AEA9F79.4070607@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Fri, 2009-10-30 at 09:10 +0100, Chris Lalancette wrote:
>  Can either you or Danny:
> 
> 1)  Get the output from stderr of qemu when this happens?  I believe qemu dumps
> the state of all of the guest fields when it's going to crash like this, and
> that can tell us if the GUEST_STATE is wrong.

<blush>
Any pointer how to produce/where to find the dump ?
</blush>


> 2)  Try the patch posted here: http://lkml.org/lkml/2009/10/28/201, and see if
> it helps?
> 

[oneliner patch manually applied]

vhost1:/usr/src/linux-2.6.32-rc5-git4# time make-kpkg kernel-image --initrd

[SNIP]

dpkg-deb: building package `linux-image-2.6.32-rc5-git4' in `../linux-image-2.6.32-rc5-git4_2.6.32-rc5-git4-10.00.Custom_amd64.deb'.
make[2]: Leaving directory `/usr/src/linux-2.6.32-rc5-git4'
make[1]: Leaving directory `/usr/src/linux-2.6.32-rc5-git4'

real    4m50.866s
user    30m3.549s
sys     2m41.270s

[REBOOT]


vhost1:~# kvm -m 512 -cdrom  /vz/template/iso/debian-503-amd64-netinst.iso -cpu pentium3
Segmentation fault
vhost1:~# dmesg| tail
handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d
handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d
handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d
handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d
handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d
handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d
handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d
handle_exception: unexpected, vectoring info 0x8000000d intr info 0x80000b0d
vmx_handle_exit: unexpected, valid vectoring info (0x8000000d) and exit reason is 0x80000021
kvm[5138]: segfault at c ip 00000000004674ac sp 0000000041cebfd0 error 4 in kvm[400000+21b000]

In my case it doesn't seem to help.

I straced the process in case that should provide some more help:
http://dth.net/supermicro/strace_2.6.32-rc5-git4_p3_cpu

Thanks for the feedback!