Bug 1569861
Summary: | Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainMemoryStats) | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Tomas Kopecek <tkopecek> | ||||
Component: | libvirt | Assignee: | Michal Privoznik <mprivozn> | ||||
Status: | CLOSED ERRATA | QA Contact: | Han Han <hhan> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 7.7 | CC: | bugzilla49, dyuan, jss, juzhou, libvirt-maint, lmen, pkrempa, pmarciniak, redhat, syzop, tkopecek, xuzhang, yafu | ||||
Target Milestone: | rc | Keywords: | Upstream | ||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | libvirt-4.4.0-1.el7 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | 1530346 | Environment: | |||||
Last Closed: | 2018-10-30 09:55:31 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: | |||||||
Bug Depends On: | 1530346 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Description
Tomas Kopecek
2018-04-20 07:13:22 UTC
We've hit (probably) same bug in our buildsystem. I'm providing some info in an attachment. It seems to be happening at least on ppc and s390x archs. RHEL 7 libvirt-3.2.0-14.el7_4.3 kernel-3.10.0-693.5.2.el7 Bug not reproduced on: libvirt-3.9.0-14.el7_5.4.x86_64 virt-manager-1.4.3-3.el7.noarch qemu-kvm-rhev-2.10.0-21.el7_5.1.x86_64 Do shutdown/start on multi VMs in parallel, no deadlock. It may be related to this bug: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1688508 . It has been fixed according to "qemu: Fix shutting down domains in parallel -- If multiple domains were being shut down in parallel, libvirtd might have deadlocked. " in libvirt-v4.1 release note. (In reply to Han Han from comment #4) > Bug not reproduced on: > libvirt-3.9.0-14.el7_5.4.x86_64 > virt-manager-1.4.3-3.el7.noarch > qemu-kvm-rhev-2.10.0-21.el7_5.1.x86_64 > Do shutdown/start on multi VMs in parallel, no deadlock. > It may be related to this bug: > https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1688508 . It has been > fixed according to "qemu: Fix shutting down domains in parallel -- If > multiple domains were being shut down in parallel, libvirtd might have > deadlocked. " in libvirt-v4.1 release note. It's not related to that. Also can not reproduce with libvirt-3.2.0-14.el7_4.9.x86_64. Tomas, can you please test with libvirt-3.9.0-9.el7 or newer? My analysis shows that this bug might be a dup of 1536461. I'd like to close it as such. We've deployed libvirt-daemon-3.9.0-14.el7_5.2 and it seems to be fixed. Thanks! Very well, I'm going to put this into POST then so that we can test it. Verified on libvirt-4.5.0-2.virtcov.el7.x86_64 qemu-kvm-rhev-2.12.0-7.el7.x86_64: 1. Parepare a running VM with qemu-guest-agent active (in vm)# systemctl status qemu-guest-agent ● qemu-guest-agent.service - QEMU Guest Agent Loaded: loaded (/usr/lib/systemd/system/qemu-guest-agent.service; disabled; > Active: active (running) since Tue 2018-07-10 16:30:30 CST; 4min 47s ago Main PID: 723 (qemu-ga) Tasks: 1 (limit: 1149) Memory: 1.8M CGroup: /system.slice/qemu-guest-agent.service └─723 /usr/bin/qemu-ga --method=virtio-serial --path=/dev/virtio-por> 2. Create serval snapshots with --disk-only --quiesce # virsh snapshot-create-as usb S1 --disk-only --quiesce Domain snapshot S1 created # virsh snapshot-create-as usb S2 --disk-only --quiesce Domain snapshot S2 created # virsh snapshot-create-as usb S3 --disk-only --quiesce Domain snapshot S3 created Check VM is running well. Verified. I mistook the bug verify of https://bugzilla.redhat.com/show_bug.cgi?id=1598084 as comment11. Please ignore it. On libvirt-4.5.0-6.el7.x86_64 qemu-kvm-rhev-2.12.0-10.el7.x86_64, verified as https://bugzilla.redhat.com/show_bug.cgi?id=1536461#c4. passed. 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. https://access.redhat.com/errata/RHSA-2018:3113 |