Bug 884650 - Add support for qemu-kvm's BALLOON_CHANGE event to avoid using monitor in virDomainGetXMLDesc
Add support for qemu-kvm's BALLOON_CHANGE event to avoid using monitor in vir...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt (Show other bugs)
6.3
x86_64 Linux
high Severity urgent
: rc
: ---
Assigned To: Jiri Denemark
Virtualization Bugs
infra
: ZStream
Depends On: 881732
Blocks: 851837 884713 888457
  Show dependency treegraph
 
Reported: 2012-12-06 08:46 EST by Dave Allan
Modified: 2016-04-26 10:26 EDT (History)
27 users (show)

See Also:
Fixed In Version: libvirt-0.10.2-12.el6
Doc Type: Bug Fix
Doc Text:
Whenever the virDomainGetXMLDesc() function was executed on a domain that was unresponsive, the call also became unresponsive. With this update, QEMU sends the BALLOON_CHANGE event when memory usage on a domain changes so that virDomainGetXMLDesc() no longer has to query an unresponsive domain. As a result, virDomainGetXMLDesc() calls no longer hang in the described scenario.
Story Points: ---
Clone Of: 881732
Environment:
Last Closed: 2013-02-21 02:28:11 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)
q64 guest xml (3.12 KB, text/plain)
2012-12-10 00:42 EST, Huang Wenlong
no flags Details
q64 guest qemu.log (31.79 KB, text/plain)
2012-12-10 00:44 EST, Huang Wenlong
no flags Details

  None (edit)
Comment 5 Huang Wenlong 2012-12-10 00:42:49 EST
Created attachment 660582 [details]
q64 guest xml
Comment 6 Huang Wenlong 2012-12-10 00:44:01 EST
Created attachment 660583 [details]
q64 guest qemu.log
Comment 7 Jiri Denemark 2012-12-11 03:19:39 EST
Looks like an issue with python bindings or python event-test example.
Comment 8 Jiri Denemark 2012-12-11 07:51:19 EST
Trivial patch that fixes the python event-test example sent for review:

http://post-office.corp.redhat.com/archives/rhvirt-patches/2012-December/msg00190.html
Comment 10 Huang Wenlong 2012-12-13 21:35:46 EST
Reproduce this bug :
libvirt-0.10.2-10.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.340.el6.x86_64

Verify this bug with :
libvirt-0.10.2-12.el6.x86_64.rpm
qemu-kvm-rhev-0.12.1.2-2.340.el6.x86_64


1) start a guest 

2) virsh setmeme --live mig 800M 

3) kill -STOP  guest-pid 

4) virsh dumpxml mig 


it can dumpxml immediately ,so mark it verified





Hi, Jiri 

I open other console with "ython /usr/share/doc/libvirt-python-0.10.2/events-python/event-test.py" 
but it can not get event about balloon change , is it the expected result ?
Comment 11 Jiri Denemark 2012-12-14 03:34:09 EST
Well, that's expected with -2.340 build of qemu-kvm, since it does not support this event. On the other hand, you should be able to reproduce this bug with that package, are you sure no virt-manager, vdsm, or anything else that would be also talking to libvirtd was running when you tried to reproduce this? You need qemu-kvm-0.12.1.2-2.344.el6 to see this bug fixed and events reported.
Comment 12 Huang Wenlong 2012-12-16 21:59:25 EST
(In reply to comment #11)
> Well, that's expected with -2.340 build of qemu-kvm, since it does not
> support this event. On the other hand, you should be able to reproduce this
> bug with that package, are you sure no virt-manager, vdsm, or anything else
> that would be also talking to libvirtd was running when you tried to
> reproduce this? You need qemu-kvm-0.12.1.2-2.344.el6 to see this bug fixed
> and events reported.



Hi, Jiri 
I re-verify this bug with :

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


step as comment 10  , I am sure there is not virt-manager or vdsm or anything else 
event handler about balloon event works well :

myDomainEventBalloonChangeCallback: Domain mig(5) 1047552
myDomainEventBalloonChangeCallback: Domain mig(5) 921600


Wenlong
Comment 13 errata-xmlrpc 2013-02-21 02:28:11 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.