From: Chris Webb <chris@arachsys.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: qemu-kvm segfaults in qemu_del_timer (0.10.5 and 0.10.6)
Date: Wed, 12 Aug 2009 17:24:01 +0100 [thread overview]
Message-ID: <20090812162401.GB8115@arachsys.com> (raw)
In-Reply-To: <4A82E200.3040107@redhat.com>
Avi Kivity <avi@redhat.com> writes:
> 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.
We're trying for this at the moment, but since we can't change the rlimit
for the running qemu-kvm processes (?), we'll have to wait until one of the
new ones dies, which may take some time. I'll follow up when I do have
something.
Cheers,
Chris.
WARNING: multiple messages have this Message-ID (diff)
From: Chris Webb <chris@arachsys.com>
To: Avi Kivity <avi@redhat.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 17:24:01 +0100 [thread overview]
Message-ID: <20090812162401.GB8115@arachsys.com> (raw)
In-Reply-To: <4A82E200.3040107@redhat.com>
Avi Kivity <avi@redhat.com> writes:
> 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.
We're trying for this at the moment, but since we can't change the rlimit
for the running qemu-kvm processes (?), we'll have to wait until one of the
new ones dies, which may take some time. I'll follow up when I do have
something.
Cheers,
Chris.
next prev parent reply other threads:[~2009-08-12 16:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 15:01 qemu-kvm segfaults in qemu_del_timer (0.10.5 and 0.10.6) Chris Webb
2009-08-12 15:01 ` [Qemu-devel] " Chris Webb
2009-08-12 15:38 ` Avi Kivity
2009-08-12 15:38 ` [Qemu-devel] " Avi Kivity
2009-08-12 16:24 ` Chris Webb [this message]
2009-08-12 16:24 ` Chris Webb
2009-08-13 12:23 ` Chris Webb
2009-08-13 12:23 ` [Qemu-devel] " Chris Webb
2009-08-13 12:41 ` Chris Webb
2009-08-13 12:41 ` [Qemu-devel] " Chris Webb
2009-08-13 12:42 ` Avi Kivity
2009-08-13 12:42 ` [Qemu-devel] " Avi Kivity
2009-08-13 12:43 ` Chris Webb
2009-08-13 12:43 ` [Qemu-devel] " Chris Webb
2009-08-13 12:45 ` Chris Webb
2009-08-13 12:45 ` [Qemu-devel] " Chris Webb
2009-08-13 12:58 ` Avi Kivity
2009-08-13 12:58 ` [Qemu-devel] " Avi Kivity
2009-08-19 22:47 ` Chris Webb
2009-08-19 22:47 ` [Qemu-devel] " Chris Webb
2009-08-24 15:45 ` Chris Webb
2009-08-24 15:45 ` [Qemu-devel] " 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=20090812162401.GB8115@arachsys.com \
--to=chris@arachsys.com \
--cc=avi@redhat.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 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.