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:
There is a flaw in the libvirt python demo program for events which can lead to a deadlock:
 
  http://www.redhat.com/archives/libvir-list/2011-January/msg00921.html

VDSM has a copy of this code as libvirtev.py and so should apply this same fix too.

Version-Release number of selected component (if applicable):
vdsm-4.9-12.2.x86_64

How reproducible:
Non-deterministically

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Opps, wrong hyperlink. This is the correct one

http://www.redhat.com/archives/libvir-list/2011-January/msg01131.html

after talking to Dan, verified the bug as follows:

- started about 30 vms 
- killed all vms using pkill 
- all qemu processes died after a seconds

[root@rhev-i32c-01 tmp]# pgrep qemu
6902
16297
47818
65964
66246
66435
66817
67058
67451
67779
68109
68419
68849
69090
69495
69941
70242
[root@rhev-i32c-01 tmp]# pkill qemu
[root@rhev-i32c-01 tmp]# pgrep qemu
47818
68849
69090
69941
70242
[root@rhev-i32c-01 tmp]# pgrep qemu

vdsm-4.9-47.el6.x86_64