qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Christophe de Dinechin <cdupontd@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: Understanding initialization order for spice in qemu
Date: Thu, 18 Jun 2020 12:30:24 +0100	[thread overview]
Message-ID: <87v9jovcfj.fsf@linaro.org> (raw)
In-Reply-To: <1D26F746-92AA-4BA4-BF92-A498DA2C67C9@redhat.com>


Christophe de Dinechin <cdupontd@redhat.com> writes:

> Hi Gerd,
>
>
> When I build qemu on master with moduels enabled, and run with spice, I occasionally see:
>
>  qemu-system-x86_64: util/module.c:136: module_load_file: Assertion `QTAILQ_EMPTY(&dso_init_list)' failed.
>
> Interestingly, I seem to have seen that only on master, but not on my
> own branch. Have you ever seen the same problem? Could there be a race
> condition here explaining why I sometimes see it, sometimes not? Or do
> you think it's more likely to be a missing build dependency? Asking
> because I don't recall ever seeing that on a clean build.

Have you switched the config in your build directory? This is one reason
to have multiple build directories outside of the source tree.

>
> Command line:
> % qemu-system-x86_64  -display spice-app /data/VMs/deb9.qcow2
>
>
>
> Thanks
> Christophe


-- 
Alex Bennée


  reply	other threads:[~2020-06-18 11:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 11:11 Understanding initialization order for spice in qemu Christophe de Dinechin
2020-06-18 11:30 ` Alex Bennée [this message]
2020-06-19  7:57 ` Gerd Hoffmann

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=87v9jovcfj.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=cdupontd@redhat.com \
    --cc=kraxel@redhat.com \
    --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).