I have a preference for just looking at the console log [for linux guests] and tracking the cpu/network/disk statistics. On Tue, Dec 2, 2014 at 6:36 PM, Stefano Maffulli <stefano at openstack.org> wrote: > [I'm bcc-ing Daniel so he can reply if he wants to be can silently drop > if he has no extra material to add to Steve's explanation. We all get > too many email :)] > > On 12/02/2014 05:48 PM, Steve Gordon wrote: > > I'll take a crack at it and then Dan can tell me how wrong I am since > > it's probably my fault it was in the etherpad ;) > [...] > > This all makes a lot of sense. So assuming writing a Windows driver is > out of question (the issue is known since 2010 and hasn't been addressed > by Intel -ahem :)) maybe for the WTE group it would be a starting point > to add documentation for the libvirtWatchdog feature available now. If > it makes sense, are there any takers? > > BTW I'm adding some of these details to the > https://wiki.openstack.org/wiki/LibvirtWatchdog so this knowledge > doesn't get lost. > > Thanks, > stef > > _______________________________________________ > Enterprise-wg mailing list > Enterprise-wg at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/enterprise-wg > -- Jason Venner Vice President and Chief Architect Mirantis Inc -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/enterprise-wg/attachments/20141202/ae5fd30b/attachment.html>