From: Avi Kivity <avi@redhat.com>
To: Chris Webb <chris@arachsys.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: qemu-kvm segfaults in qemu_del_timer (0.10.5 and 0.10.6)
Date: Wed, 12 Aug 2009 18:38:40 +0300 [thread overview]
Message-ID: <4A82E200.3040107@redhat.com> (raw)
In-Reply-To: <20090812150159.GW5348@arachsys.com>
On 08/12/2009 06:01 PM, Chris Webb wrote:
> I have a couple of clusters hosting qemu-kvm virtual machines. One of these
> clusters consists of dual quad-core Xeon E5420s (vmx), the other consists of
> dual quad-core Barcelona Opterons (svm), and both are running x86-64 Linux
> 2.6.30.4 with the kvm modules included with the upstream kernel compiled in.
>
> Running qemu-kvm 0.10.5, I was seeing occasional segfaults from the virtual
> machines, perhaps two or three a day across each cluster. The guest OS didn't
> appear to be a factor, as both Linux and Windows VMs have crashed. I then
> switched to the recently released qemu-kvm 0.10.6, and am still seeing these
> segfaults.
>
> It's very hard for me to arrange for core dumps on these live clusters, and the
> segfaults are hard to reproduce on test machines because they are rare.
> However, I have unstripped copies of the respective binaries and have used gdb
> to translate the segfault ip into a source file and line number, which I hope
> might be useful. On both clusters and for each version of qemu-kvm, segfaults
> are happening at lines #1161 and #1163 of vl.c:
>
I understand it's hard, but it's nearly impossible to work out the
problem from so little data, so please do make the effort to obtain dumps.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-12 15:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 15:01 [Qemu-devel] qemu-kvm segfaults in qemu_del_timer (0.10.5 and 0.10.6) Chris Webb
2009-08-12 15:38 ` Avi Kivity [this message]
2009-08-12 16:24 ` [Qemu-devel] " Chris Webb
2009-08-13 12:23 ` Chris Webb
2009-08-13 12:41 ` Chris Webb
2009-08-13 12:42 ` Avi Kivity
2009-08-13 12:43 ` Chris Webb
2009-08-13 12:45 ` Chris Webb
2009-08-13 12:58 ` Avi Kivity
2009-08-19 22:47 ` Chris Webb
2009-08-24 15:45 ` Chris Webb
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=4A82E200.3040107@redhat.com \
--to=avi@redhat.com \
--cc=chris@arachsys.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).