From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=42235 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OorTf-0004aq-JY for qemu-devel@nongnu.org; Fri, 27 Aug 2010 01:27:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OorTe-0000yd-Fa for qemu-devel@nongnu.org; Fri, 27 Aug 2010 01:27:47 -0400 Received: from mx1.redhat.com ([209.132.183.28]:17796) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OorTe-0000yC-9P for qemu-devel@nongnu.org; Fri, 27 Aug 2010 01:27:46 -0400 From: Amit Shah Date: Fri, 27 Aug 2010 10:57:08 +0530 Message-Id: Subject: [Qemu-devel] [PATCH v3 0/3] virtio-balloon: Don't wait indefinitely for guest response List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu list Cc: Luiz Capitulino , agl@us.ibm.com, Amit Shah , Paolo Bonzini Since I didn't get negative reactions to the patch I posted yesterday, here's the complete series. It adds a qerror message that mentions the machine is stopped or the guest is slow to respond, so the stats should be assumed to be old. The error report is sent out before the stats, I don't think we do that for any other command. libvirt should be prepared to handle this. If not, please suggest a better alternative. Differences from v2: - Add a timeout for uncooperative/hung guests - Add an qerror message for letting users/management know of guest stopped status. Amit Shah (3): balloon: Don't try fetching info if guest is unresponsive qerror: Add a new MACHINE_STOPPED error message balloon: Don't try fetching info if machine is stopped balloon.c | 11 +++++++---- balloon.h | 6 ++++-- hw/virtio-balloon.c | 21 +++++++++++++++++++-- qerror.c | 4 ++++ qerror.h | 3 +++ 5 files changed, 37 insertions(+), 8 deletions(-) -- 1.7.2.2