https://bugzilla.novell.com/show_bug.cgi?id=763898 https://bugzilla.novell.com/show_bug.cgi?id=763898#c2 James Fehlig <jfehlig@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|jfehlig@suse.com |marcus.husar@googlemail.com --- Comment #2 from James Fehlig <jfehlig@suse.com> 2012-06-22 22:13:39 UTC --- (In reply to comment #0)
After a period of time my KVM guests (OpenSuSE 12.1 and Debian Squeeze, both x64_64) appear to be unresponsive. The host system uses OpenSuSE 12.1, too.
Do you mean the guests are hung? E.g. can't ping, ssh, interact via serial console, etc? Do you notice any problems on the host? Is libvirt responsive? E.g. virsh list, virsh dominfo, ...?
After some additional searching I found a second matching bug report: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=757382
That bug is a libvirtd hang. Do you see that? Even so, guests shouldn't become unresponsive. You can start guests and then kill off libvirtd afterall.
Some lines in my libvirtd.log are found in the Fedora bug report above.
18:18:30.967: 2393: error : virNetSocketReadWire:912 : End of file while reading data: Input/output error 18:18:36.960: 2393: error : virNetSocketReadWire:912 : End of file while reading data: Input/output error 18:19:04.000: 2394: error : qemuDomainObjBeginJobInternal:772 : Timed out during operation: cannot acquire state change lock
I don't think these are fatal. Should be warning or something.
18:19:05.893: 2393: error : qemuMonitorIO:577 : internal error End of file from monitor
This is always seen when a guest terminates.
18:19:15.232: 2395: warning : qemuDomainObjTaint:1110 : Domain id=3 name='virtual1' uuid=7c7f469c-3d57-7bf5-c81a-d815966a948b is tainted: high-privileges
And seen when the guest starts if /etc/libvirt/qemu.conf is configured with user="root and group="root", which you must have set since the default for 12.1 is to launch qemu instances as qemu:qemu.
When I try to restart the guest (virsh restart virtual1) it says: Fehler: Neustart der Domain virtual1 gescheitert (restart of domain failed) Fehler: Timed out during operation: cannot acquire state change lock
Is a qemu-kvm process still running for the guest? What state does libvirt think the guest is in (virsh dominfo)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.