From: Paolo Bonzini <pbonzini@redhat.com>
To: Wesley Holevinski <Wesley@adaptiveapps.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Assertion failure in qemu-char.c
Date: Mon, 20 Jan 2014 15:07:29 +0100 [thread overview]
Message-ID: <52DD2DA1.2030707@redhat.com> (raw)
In-Reply-To: <8FF4391EB0AF584FB28E47D0332071086E6D02@AA-Xch01.adaptiveapps.com>
Il 20/01/2014 13:37, Wesley Holevinski ha scritto:
>
> Hi all,
>
> I'm running into an issue that's causing my guests to crash while
> using vm-channels. There is an assertion that's failing in qemu-char.c,
> that, when it happens causes my guest to go down. The error can be seen
> in the host-side logs.
>
> Rather than being too wordy on-list, here's a link to a bug I opened
> against qemu-kvm: https://bugs.launchpad.net/qemu/+bug/1268671
Unfortunately, RHEL/CentOS support is not provided by these mailing
lists. RHEL/CentOS backport features on top of old versions of QEMU,
and thus it is quite hard to provide support here.
You also aren't describing if doing anything specifically will cause the
crash.
As an initial step, you could download QEMU 1.7 and try to reproduce the
bug there. That would help.
> I apologize if this isn't the right list for this, but I'm trying to
> get more eyes on this since guests crashing seems like a critical issue IMO.
>
> Also take note of the comment in the source; there is a comment about
> how the snippet of code that's failing exists because of a bug in
> glib. Can anyone provide more info on that glib bug?
You can find some information at
https://bugzilla.gnome.org/show_bug.cgi?id=626702#c6.
Paolo
next parent reply other threads:[~2014-01-20 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8FF4391EB0AF584FB28E47D0332071086E6D02@AA-Xch01.adaptiveapps.com>
2014-01-20 14:07 ` Paolo Bonzini [this message]
2014-01-20 14:38 ` [Qemu-devel] Assertion failure in qemu-char.c Wesley Holevinski
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=52DD2DA1.2030707@redhat.com \
--to=pbonzini@redhat.com \
--cc=Wesley@adaptiveapps.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).