[libvirt] Syslog "nested job is dangerous" message
Jiri Denemark
jdenemar at redhat.com
Thu Jul 17 06:51:44 UTC 2014
On Thu, Jul 17, 2014 at 13:29:52 +1000, Sam Bobroff wrote:
> On 17/07/14 12:50, Eric Blake wrote:
> > On 07/16/2014 07:52 PM, Sam Bobroff wrote:
> >> Hello everyone,
> >
> > [Can you configure your mailer to wrap long lines?]
>
> [No problem, done.]
>
> >> After performing a migration, the syslog often contains several
> >> messages like this:
> >>
> >> "This thread seems to be the async job owner; entering monitor
> >> without asking for a nested job is dangerous"
> >
> > The sign of a bug that we need to fix. What version of libvirt are
> > you using? We may have already fixed it.
>
> I've been testing on 1.2.6, but I will re-test on the latest code from git.
Hmm, it what were you doing when the message appeared in the log? I
fixed wrong usage of our job tracking APIs long time ago
(e4e28220b572cf4c71d07740c24150411f0704a6 in 1.0.3) so I guess there
must be another place we don't do it correctly.
Jirka
More information about the libvir-list
mailing list