From 4a5d7d9858d407582917edcf7473f63a0bad5566 Mon Sep 17 00:00:00 2001
From: Chris Sosa <sosa@chromium.org>
Date: Thu, 9 Dec 2010 15:46:09 -0800
Subject: [PATCH] Wait for child to exit after killing it.

Use general purpose wait in case your connecting to a vm
that you didn't start.

Change-Id: Ie67e2d3235882d372d04e4a44d0781ddfc8d4645

BUG=chromium-os:10121
TEST=Ran it, caused some crashes.  Still ran test after retries.

Review URL: http://codereview.chromium.org/5757001
---
 lib/cros_vm_lib.sh | 21 ++++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/lib/cros_vm_lib.sh b/lib/cros_vm_lib.sh
index d28539c14d..3048c3dd30 100644
--- a/lib/cros_vm_lib.sh
+++ b/lib/cros_vm_lib.sh
@@ -19,6 +19,25 @@ function get_pid() {
   sudo cat "${KVM_PID_FILE}"
 }
 
+# General purpose blocking kill on a pid.
+# This function sends a specified kill signal [0-9] to a pid and waits for it
+# die up to a given timeout.  It exponentially backs off it's timeout starting
+# at 1 second.
+# $1 the process id.
+# $2 signal to send (-#).
+# $3 max timeout in seconds.
+# Returns 0 on success.
+function blocking_kill() {
+  local timeout=1
+  sudo kill -$2 $1
+  while ps -p $1 > /dev/null && [ ${timeout} -le $3 ]; do
+    warn "Process still running, sleeping for ${timeout}"
+    sleep ${timeout}
+    timeout=$((timeout*2))
+  done
+  ! ps -p ${1} > /dev/null
+}
+
 # TODO(rtc): These flags assume that we'll be using KVM on Lucid and won't work
 # on Hardy.
 # $1: Path to the virtual image to start.
@@ -98,7 +117,7 @@ function stop_kvm() {
     local pid=$(get_pid)
     if [ -n "${pid}" ]; then
       echo "Killing ${pid}" >&2
-      sudo kill ${pid}
+      blocking_kill ${pid} 1 16 || blocking_kill 9 1
       sudo rm "${KVM_PID_FILE}"
     else
       echo "No kvm pid found to stop." >&2