Bug 1883464
Summary: | Hit error when shutdown 100 VMs and run `virsh domstats` concurrently | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | chhu | ||||||
Component: | libvirt | Assignee: | 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.0 | Keywords: | 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
chhu
2020-09-29 09:53:20 UTC
Created attachment 1717488 [details]
libvirtd.log
Created attachment 1717489 [details]
qemu-guest.log
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. 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. 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. |