This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-changelog] The following patch adds a section for SHUTDOWN OPTIONS

To: xen-changelog@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-changelog] The following patch adds a section for SHUTDOWN OPTIONS for the xmdomain.cfg
From: Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 01 Nov 2005 17:36:13 +0000
Delivery-date: Tue, 01 Nov 2005 17:34:46 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-changelog-request@lists.xensource.com?subject=help>
List-id: BK change log <xen-changelog.lists.xensource.com>
List-post: <mailto:xen-changelog@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=unsubscribe>
Reply-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-changelog-bounces@xxxxxxxxxxxxxxxxxxx
# HG changeset patch
# User kaf24@xxxxxxxxxxxxxxxxxxxx
# Node ID b818029835dedb7fac8a5299fffe203aee861092
# Parent  07b5b3e2ff451f2ae2d5f73acd0787a1b7b3c68f
The following patch adds a section for SHUTDOWN OPTIONS for the xmdomain.cfg
man page.  It documents the new set of options introduced over the last few

Signed-off-by: Sean Dague <sean@xxxxxxxxx>

diff -r 07b5b3e2ff45 -r b818029835de docs/man/xmdomain.cfg.pod.5
--- a/docs/man/xmdomain.cfg.pod.5       Tue Nov  1 09:34:34 2005
+++ b/docs/man/xmdomain.cfg.pod.5       Tue Nov  1 09:36:19 2005
@@ -72,6 +72,57 @@
 =item I<builder>
+There are 3 options which control domain shutdown (both planned and
+unplanned) under certain events.  The 3 events currently captured are:
+=over 4
+=item I<shutdown>
+Triggered on either an I<xm shutdown> or graceful shutdown from inside
+the DomU.
+=item I<reboot>
+Triggered on either an I<xm reboot> or graceful reboot from inside the
+=item I<crash>
+Triggered when a DomU goes to the crashed state for any reason.
+All of them take one of 4 valid states listed below.  
+=over 4
+=item I<destroy>
+The domain will be cleaned up completely.  No attempt at respawning
+will occur.  This is what a typical shutdown would look like.
+=item I<restart>
+The domain will be restarted with the same name as the old domain.
+This is what a typical reboot would look like.
+=item I<preserve>
+The domain will not be cleaned up at all.  This is often useful for
+crash state domains which ensures that enough evidence is to debug the
+real issue.
+=item I<rename-restart>
+The old domain will not be cleaned up, but will be renamed so a new
+domain can be restarted in it's place.  (TODO: what does this mean for
+resources?  What is the renamed name?)
 =head1 SEE ALSO

Xen-changelog mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-changelog] The following patch adds a section for SHUTDOWN OPTIONS for the xmdomain.cfg, Xen patchbot -unstable <=