RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Libvirt uses incorrect async job type when restarting CPUs of the guest after taking an external checkpoint is done.


Version-Release number of selected component (if applicable):
libvirt-0.10.2-11.el6.x86_64


How reproducible:
100%


Steps to Reproduce:
1. start a guest
2. virsh snapshot-create-as guest --memspec=/tmp/test.img
3.
  
Actual results:
$ grep libvirt /var/log/messages | grep warn 
Dec  7 11:14:44 angien libvirtd: 3989: warning : qemuDomainObjEnterMonitorInternal:1005 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous

Expected results:
No warning printed.


Additional info:
This is a bug in a new feature. Fix submitted upstream: http://www.redhat.com/archives/libvir-list/2012-December/msg00331.html

Fixed upstream:

commit 46b0c93332fb16fd9f64cd9b3bb95a0990145f0c
Author: Peter Krempa <pkrempa>
Date:   Fri Dec 7 11:50:52 2012 +0100

    qemu: Restart CPUs with valid async job type when doing external snapshots
    
    When restarting CPUs after an external snapshot, the restarting function
    was called without the appropriate async job type. This caused that a
    new sync job wasn't created and allowed races in the monitor.

Verify this bug with:

libvirt-0.10.2-12.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.340.el6.x86_64

1)start a guest
2. virsh snapshot-create-as guest --memspec=/tmp/test.img
3.  grep libvirt /var/log/messages | grep warn 
there is not warning message like : 
"qemuDomainObjEnterMonitorInternal:1005 : This thread seems to be the async job owner; entering monitor without asking for a nested job is dangerous"

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0276.html