Index: trunk/packages/sipb-xen-remote-server/debian/changelog
===================================================================
--- trunk/packages/sipb-xen-remote-server/debian/changelog	(revision 1161)
+++ trunk/packages/sipb-xen-remote-server/debian/changelog	(revision 1163)
@@ -1,2 +1,10 @@
+sipb-xen-remote-server (0.10.2) unstable; urgency=low
+
+  * There's a race condition for if the VM gets powered off between the
+    listvms and the actual request. Solve the problem correctly by using a
+    non-conflicting error code to indicate an invalid command
+
+ -- Evan Broder <broder@mit.edu>  Wed, 22 Oct 2008 00:46:38 -0400
+
 sipb-xen-remote-server (0.10.1) unstable; urgency=low
 
Index: trunk/packages/sipb-xen-remote-server/files/usr/sbin/sipb-xen-remote-control
===================================================================
--- trunk/packages/sipb-xen-remote-server/files/usr/sbin/sipb-xen-remote-control	(revision 1161)
+++ trunk/packages/sipb-xen-remote-server/files/usr/sbin/sipb-xen-remote-control	(revision 1163)
@@ -31,6 +31,9 @@
     (out, err) = p.communicate()
     if p.returncode == 1:
+        print >>sys.stderr, "machine '%s' is not on" % machine_name
+        return 1
+    elif p.returncode == 34:
         print >>sys.stderr, "ERROR: invalid command"
-        return 1
+        return 34
     sys.stderr.write(err)
     sys.stdout.write(out)