[libvirt-users] Reg: Libvirt API does not return, after qemu-kvm is hungup.

[Alphonse Hansel Anthony]

Hi All,

   I am facing the following issue, while using Libvirt version 0.8.4.
(1) Libvirt API does not return, since the qemu-kvm process is hung up.

Based on the information available on mail thread
*https://bugzilla.redhat.com/show_bug.cgi?id=676205* (comment 26 - scenario
1),
this has been fixed in later version of Libvirt, specifically in RHEL
6.2(libvirt 0.9.4).

I have checked the changelogs between version 0.8.7(RHEL 6.1) & 0.9.4 and
was not able to identify the related patch information.

Please let me know, If I am looking at the wrong version for this fix?

Any help in this regard, would be useful.

Thanks,
Alphonse

Comment reference:
--SNIP--

1. The QEMU process has hung.

        QEMU won't respond to monitor commands. The API call making
the first monitor command will wait forever, any subsequent API calls
issuing monitor commands will timeout after ~30 seconds with this
libvirt error message.

        This is expected behaviour when QEMU has hung.

--SNIP--

In RHEL-6.2 we have done a number of things to address / mitigate these problems

 - It is now always possible to destroy a guest, even if the monitor
is stuck. This lets you destroy a guest in scenario 1, which is not
always possible with RHEL-5 libvirt, without restarting libvirtd.

--SNIP--

--EOF--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20120910/60e00711/attachment.htm>