Red Hat Bugzilla – Bug 884650
Add support for qemu-kvm's BALLOON_CHANGE event to avoid using monitor in virDomainGetXMLDesc
Last modified: 2016-04-26 10:26:44 EDT
Created attachment 660582 [details] q64 guest xml
Created attachment 660583 [details] q64 guest qemu.log
Looks like an issue with python bindings or python event-test example.
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
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 ?
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.
(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
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