[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Understanding initialization order for spice in qemu
From: |
Alex Bennée |
Subject: |
Re: Understanding initialization order for spice in qemu |
Date: |
Thu, 18 Jun 2020 12:30:24 +0100 |
User-agent: |
mu4e 1.5.3; emacs 28.0.50 |
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