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
--
libvir-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/libvir-list
