On Tue, May 24, 2011 at 06:06:40PM +0100, Daniel P. Berrange wrote:
An update of
https://www.redhat.com/archives/libvir-list/2011-May/msg00657.html
Currently when libvirt has a serious error doing I/O and/or parsing of the QEMU monitor, it will kill off the guest. Application developers have expressed a desire for more graceful handling of this scenario. In particular to allow the guest OS to continue to run, without any further monitor interactons, and then kill/restart it at a time which is convenient to the guest admin/apps.
New in this posting:
- Change the name of the event to 'CONTROL_ERROR' and use the generic callback, instead of passing a type field - Add python dispatch code - Add 3rd patch to improve qemu monitor error reporting
Okay reviewed, principle sounds good we can probably use the event for other hypervisors. I just had to modify 1/3 to add a description of the event message in the protocol ABI check file src/remote_protocol-structs ACK, and pushed, Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel@veillard.com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/