From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jim Fehlig <jfehlig@novell.com>
Subject: [PATCH] [xend] fix coredump-{restart,
	destroy} on_crash actions
Date: Tue, 27 Jul 2010 09:09:11 -0600
Message-ID: <4C4EF697.8060506@novell.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="------------050205040300090208090908"
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

This is a multi-part message in MIME format.
--------------050205040300090208090908
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

After all of these years, more fallout from xen-api and legacy xmlrpc
integration.  Can't say I'll miss xend :-).

Please apply to xen-4.0-testing.

Regards,
Jim



--------------050205040300090208090908
Content-Type: text/x-patch;
 name="xend-crash-behavior.patch"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="xend-crash-behavior.patch"

# HG changeset patch
# User Jim Fehlig <jfehlig@novell.com>
# Date 1280165174 21600
# Node ID 3da5c666fb1ba1f532803e59040e7a0d8481c2ba
# Parent  ac7e4c6ec6c7494e4046da92aa8f62f6c1371438
The xm documentation and example config files state that possible
"on crash" behaviors include coredump-{restart,destroy},
but domain creation will fail if either of these options are
specified

xen52:~ # grep coredump /etc/xen/vm/test
on_crash="coredump-restart"
xen52:~ # xm create /etc/xen/vm/test
Using config file "/etc/xen/vm/test".
Error: Invalid argument.

coredump-and-{restart,destroy} are permissible but unnecessarily
verbose and inconsistent with documentation.  This patch simply
adds coredump-{restart,destroy} to the list of permissible values.

    Signed-off-by: Jim Fehlig <jfehlig@novell.com>

diff -r ac7e4c6ec6c7 -r 3da5c666fb1b tools/python/xen/xend/XendAPIConstants.py
--- a/tools/python/xen/xend/XendAPIConstants.py	Fri Jul 23 19:23:49 2010 +0100
+++ b/tools/python/xen/xend/XendAPIConstants.py	Mon Jul 26 11:26:14 2010 -0600
@@ -45,8 +45,10 @@
 XEN_API_ON_CRASH_BEHAVIOUR = [
     'destroy',
     'coredump_and_destroy',
+    'coredump_destroy',
     'restart',
     'coredump_and_restart',
+    'coredump_restart',
     'preserve',
     'rename_restart'
 ]

--------------050205040300090208090908
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

--------------050205040300090208090908--