Bug 1883464

Summary: Hit error when shutdown 100 VMs and run `virsh domstats` concurrently
Product: Red Hat Enterprise Linux 9 Reporter: chhu
Component: libvirtAssignee: khanicov
libvirt sub component: General QA Contact: yafu <yafu>
Status: CLOSED MIGRATED Docs Contact:
Severity: medium    
Priority: medium CC: dyuan, jsuchane, lmen, mprivozn, virt-maint, xuzhang, yafu, yalzhang
Version: 9.0Keywords: MigratedToJIRA, Triaged
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: libvirt_RHV_INT
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-22 17:32:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
libvirtd.log
none
qemu-guest.log none

Description chhu 2020-09-29 09:53:20 UTC
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)

Comment 1 chhu 2020-09-29 09:59:50 UTC
Created attachment 1717488 [details]
libvirtd.log

Comment 2 chhu 2020-09-29 10:00:31 UTC
Created attachment 1717489 [details]
qemu-guest.log

Comment 4 Michal Privoznik 2020-10-12 07:06:40 UTC
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.

Comment 5 John Ferlan 2021-09-08 13:30:20 UTC
Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release.

Comment 7 RHEL 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 8 RHEL 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.