[libvirt] Syslog "nested job is dangerous" message

Sam Bobroff sam.bobroff at au1.ibm.com
Thu Jul 17 01:52:31 UTC 2014

Hello everyone,

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 message makes it sound as if the user has done something dangerous but, after looking at the code that produces the message, it appears to be more to do with how the libvirt job code is used.

The commit that added the warning (6eede368bc8e3df2c94c2ec1a913885ce08e99db) doesn't explain why it might be dangerous...

    qemu: Warn on possibly incorrect usage of EnterMonitor*                                      
    qemuDomainObjEnterMonitor{,WithDriver} should not be called from async                      
    jobs, only EnterMonitorAsync variant is allowed.              

... so I would appreciate some advice from people who understand that area.

Would it be appropriate to re-word the message, or perhaps change it to a debug message so that it's not normally seen by users?

Is it important to track down the cases that are generating the warning and fix them? (Could it cause some kind of significant problem?)


More information about the libvir-list mailing list