From: Danny ter Haar <dth@dth.net>
To: Chris Lalancette <clalance@redhat.com>
Cc: Ryan Harper <ryanh@us.ibm.com>, Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org
Subject: Re: kvm problems on new hardware
Date: Fri, 30 Oct 2009 09:54:11 +0100 [thread overview]
Message-ID: <1256892851.15399.17.camel@thinkpaddth> (raw)
In-Reply-To: <4AEA9F79.4070607@redhat.com>
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!
next prev parent reply other threads:[~2009-10-30 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 10:06 kvm problems on new hardware Danny ter Haar
2009-10-27 9:45 ` Avi Kivity
2009-10-27 9:58 ` Danny ter Haar
2009-10-27 10:27 ` Danny ter Haar
2009-10-27 10:34 ` Avi Kivity
2009-10-27 10:47 ` Danny ter Haar
2009-10-29 18:37 ` Danny ter Haar
2009-10-29 22:07 ` Ryan Harper
2009-10-30 0:23 ` Danny ter Haar
2009-10-30 8:10 ` Chris Lalancette
2009-10-30 8:54 ` Danny ter Haar [this message]
2009-11-04 10:43 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1256892851.15399.17.camel@thinkpaddth \
--to=dth@dth.net \
--cc=avi@redhat.com \
--cc=clalance@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=ryanh@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.