[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 1268671] Re: CentOS guest crashing due to assertion fa

From: Paolo Bonzini
Subject: [Qemu-devel] [Bug 1268671] Re: CentOS guest crashing due to assertion failure in qemu-char.c
Date: Thu, 12 Jan 2017 08:56:52 -0000

It's a glib bug.  It's fixed in RHEL 6.9 beta and in due time the fix
will get to CentOS.

** Changed in: qemu
       Status: Incomplete => Invalid

** Bug watch added: Red Hat Bugzilla #1212722

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  CentOS guest crashing due to assertion failure in qemu-char.c

Status in QEMU:

Bug description:
  Here is the log in /var/log/libvirt/qemu/centos_heavy.log

  qemu-kvm: /builddir/build/BUILD/qemu-kvm- 
io_watch_poll_finalize: Assertion `iwp->src == ((void *)0)' failed.
  2014-01-13 16:50:31.576+0000: shutting down

  The code it's failing the assertion on has an interesting comment:

      static void io_watch_poll_finalize(GSource *source)
      /* Due to a glib bug, removing the last reference to a source
      * inside a finalize callback causes recursive locking (and a
      * deadlock). This is not a problem inside other callbacks,
      * including dispatch callbacks, so we call io_remove_watch_poll
      * to remove this source. A t this point, iwp->src must
      * be NULL, or we would leak it.
      * This would be solved much more elegantly by child sources,
      * but we support older glib versions that do not have them.
      IOWatchPoll *iwp = io_watch_poll_from_source(source);
      assert(iwp->src == NULL);

  CPU Info:



  Relevant RPM versions:



  Domain config:


  (Note the use of the vmchannels; I believe this is playing a part in
  this crash)


  uname -a:

  Linux blizzard 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC
  2014 x86_64 x86_64 x86_64 GNU/Linux


  CLI to start guest (included in attached dump):



  thread apply all bt:


To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]