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.
Description of problem:
Hit error when shutdown 100 VMs and run `virsh domstats` concurrently,
"error: internal error: End of file from qemu monitor
error: Unable to read from monitor: Connection reset by peer".
Version-Release number of selected component (if applicable):
libvirt-6.6.0-6.module+el8.3.0+8125+aefcf088.x86_64
qemu-kvm-5.1.0-9.module+el8.3.0+8182+ac9ced32.x86_64
kernel: 4.18.0-234.el8.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Start 100 VMs
2. Run domstats.sh to get all domain stats on one terminal
# cat domstats.sh
#!/bin/sh
for i in {1..50}
do
virsh domstats 2>&1 >>stats.log
sleep 2
done
#sh domstats.sh
3. On another terminal, shutdown 100 VMs concurrently
# for i in $(virsh list --name); do virsh shutdown $i & done
4. Get error in libvirtd.log and on the terminal which is running domstats.sh
-------------------------------------------------------------------
# sh domstats.sh
error: internal error: End of file from qemu monitor
error: Unable to read from monitor: Connection reset by peer
error: Unable to read from monitor: Connection reset by peer
error: Unable to read from monitor: Connection reset by peer
--------------------------------------------------------------------
Actual results:
In Step4, Get error in libvirtd.log
Expected results:
In Step4, No error.
Additional info:
- libvirtd.log
- qemu guest log
- In step2 run `python3 domstats.py`, hit same error.
# cat domstats.py
import libvirt
import time
conn = libvirt.open("qemu:///system")
for x in range(1,100):
print(conn.getAllDomainStats())
time.sleep(2)
Just for the record, I helped Chenli debug this and the problem is how libvirt deals with monitor disappearing during domstats. While we check whether monitor is available when getting stats for a domain, we do it upfront and don't take into account that it may disappear between two stat callbacks.
Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release.
Comment 7RHEL Program Management
2023-09-22 17:31:10 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 8RHEL Program Management
2023-09-22 17:32:54 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Description of problem: Hit error when shutdown 100 VMs and run `virsh domstats` concurrently, "error: internal error: End of file from qemu monitor error: Unable to read from monitor: Connection reset by peer". Version-Release number of selected component (if applicable): libvirt-6.6.0-6.module+el8.3.0+8125+aefcf088.x86_64 qemu-kvm-5.1.0-9.module+el8.3.0+8182+ac9ced32.x86_64 kernel: 4.18.0-234.el8.x86_64 How reproducible: 100% Steps to Reproduce: 1. Start 100 VMs 2. Run domstats.sh to get all domain stats on one terminal # cat domstats.sh #!/bin/sh for i in {1..50} do virsh domstats 2>&1 >>stats.log sleep 2 done #sh domstats.sh 3. On another terminal, shutdown 100 VMs concurrently # for i in $(virsh list --name); do virsh shutdown $i & done 4. Get error in libvirtd.log and on the terminal which is running domstats.sh ------------------------------------------------------------------- # sh domstats.sh error: internal error: End of file from qemu monitor error: Unable to read from monitor: Connection reset by peer error: Unable to read from monitor: Connection reset by peer error: Unable to read from monitor: Connection reset by peer -------------------------------------------------------------------- Actual results: In Step4, Get error in libvirtd.log Expected results: In Step4, No error. Additional info: - libvirtd.log - qemu guest log - In step2 run `python3 domstats.py`, hit same error. # cat domstats.py import libvirt import time conn = libvirt.open("qemu:///system") for x in range(1,100): print(conn.getAllDomainStats()) time.sleep(2)