From mboxrd@z Thu Jan 1 00:00:00 1970 From: Emmanuel Lacour Subject: Re: Detect guest panic Date: Tue, 18 Nov 2008 17:49:22 +0100 Message-ID: <20081118164922.GO1897@easter-eggs.com> References: <20081118153645.GM1897@easter-eggs.com> <4922EFC7.9030803@mair-family.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: kvm@vger.kernel.org Return-path: Received: from volubilis.easter-eggs.org ([212.85.154.90]:53185 "EHLO volubilis.easter-eggs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754121AbYKRQtY (ORCPT ); Tue, 18 Nov 2008 11:49:24 -0500 Received: from localhost (localhost [127.0.0.1]) by volubilis.easter-eggs.org (Postfix) with ESMTP id DD2212432D for ; Tue, 18 Nov 2008 17:49:23 +0100 (CET) Received: from datura.easter-eggs.fr (vbo91-5-88-186-16-26.fbx.proxad.net [88.186.16.26]) by volubilis.easter-eggs.org (Postfix) with ESMTP id 889C624310 for ; Tue, 18 Nov 2008 17:49:23 +0100 (CET) Content-Disposition: inline In-Reply-To: <4922EFC7.9030803@mair-family.org> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, Nov 18, 2008 at 09:39:35AM -0700, David Mair wrote: >> > If the guest has a reachable IP address the simplest way might be to > ping the guest from the host every so often and, if it stops responding > for long enough to make you believe it has frozen, kill the qemu process > and run it again. I suppose you could also expose the qemu console via a > socket or other host file descriptor then you can have the pinging > program on the host try to reset the guest without killing the qemu > process. > Thanks for your help, but ping is not enough, if it doesn't answer it doesn't mean that the WM is crashed, it can means that only the network is crashed (and I have this kind of problems too (see other recent thread for virtio_net ;)) and I have other fixes for those kind of problems. Well I'm looking for some sort of "watchdog" kvm device ;)