On Wed, Apr 08, 2009 at 09:18:55AM -0500, Anthony Liguori wrote:
Daniel P. Berrange wrote:
On Tue, Apr 07, 2009 at 04:19:42PM -0500, Hollis Blanchard wrote:
Hi Rich, your watchdog qemu patch is working fine for me (i6300esb, default reset behavior), but I was wondering... how should libvirt find out about the watchdog firing?
This falls into the general problem space of how does QEMU notify its management app of interesting events. We already really want the ability to be notify of ENOSPC errors in disks, and also would like to know if the VM is paused for any reason outside our control. There have been proposals to just print an async message to the monitor upon events, that mgmt app could then parse. This is a little fragile though, so for a long term solutiuon we really need the generic libqemumonitor.so type API with formal async notification support.
I just posted a patch series that demonstrate how I think it should work. FWIW, I think notifications are orthogonal to libqemumonitor.so and a non-human monitor mode.
If we get a way to have async events without waiting for libqemumonitor.so that'd make me very happy :-) Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|