Bug 22789 – libvirtd: Timed out during operation: cannot acquire state change lock

Bug 22789 - libvirtd: Timed out during operation: cannot acquire state change lock


Summary:	libvirtd: Timed out during operation: cannot acquire state change lock

Status:	CLOSED WORKSFORME

Product:	UCS
Classification:	Unclassified
Component:	Virtualization - UVMM
Version:	UCS 3.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Bugzilla Mailingliste
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2011-06-21 09:41 CEST by Arvid Requate
Modified:	2023-06-28 10:46 CEST (History)
CC List:	5 users (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Arvid Requate

2011-06-21 09:41:55 CEST

Auf einem Testsystem hängt der libvirtd, virsh Befehle bekommen einen timeout:

virsh destroy output:
error: Failed to destroy domain e09f620c-9854-5b17-a036-0710b3ac2464
error: Timed out during operation: cannot acquire state change lock

Auch ein univention-virtual-machine-manager-node-common restart beendet den Prozess nicht, der Zustand lässt sich nur durch ein SIGKILL beheben.

Laut https://bugzilla.redhat.com/show_bug.cgi?id=676205 ist das Verhalten in 0.9.0 verbessert.

<phahn>: Ich vermute mal "[libvirt] [PATCH 3/6] use virObject to manage reference-count of virDomainObj" aka "[PATCH] qemu: fix a dead-lock problem", weil das genau im Fehlerfall auftritt.

Hinweis zum Debugging:

<phahn>: Da "libvirtd" multi-threaded ist, ist ein strace auf dem Haupt-thread wenig aussagekräftig, da dieser i.d.R. nur auf das Beenden der gestarteten anderen Threads wartet. Von daher in so einem Fall zusätzlich "-f" angeben, um alle Threads zu tracen!


+++ This bug was initially created as a clone of Bug #22747 +++

Comment 1 Stefan Gohmann

2013-04-03 21:26:33 CEST

In UCS 3.1 wurde libvirt aktualisiert. Falls das erneut auftritt, bitte Reopen.