Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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.
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
Created attachment 660582 [details] q64 guest xml