Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 885081 - Invalid job handling while restarting CPUs when creating external snapshot
Invalid job handling while restarting CPUs when creating external snapshot
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt (Show other bugs)
6.4
Unspecified Unspecified
high Severity high
: rc
: ---
Assigned To: Peter Krempa
Virtualization Bugs
:
Depends On:
Blocks: 888457
  Show dependency treegraph
 
Reported: 2012-12-07 08:09 EST by Peter Krempa
Modified: 2013-02-21 02:28 EST (History)
9 users (show)

See Also:
Fixed In Version: libvirt-0.10.2-12.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-02-21 02:28:19 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0276 normal SHIPPED_LIVE Moderate: libvirt security, bug fix, and enhancement update 2013-02-20 16:18:26 EST

  None (edit)
Description Peter Krempa 2012-12-07 08:09:28 EST
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
Comment 2 Peter Krempa 2012-12-11 05:34:03 EST
Fixed upstream:

commit 46b0c93332fb16fd9f64cd9b3bb95a0990145f0c
Author: Peter Krempa <pkrempa@redhat.com>
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.
Comment 5 Huang Wenlong 2012-12-12 22:46:47 EST
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"
Comment 6 errata-xmlrpc 2013-02-21 02:28:19 EST
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

Note You need to log in before you can comment on or make changes to this bug.