[Xen-changelog] Added description of the behaviour of rename-restart.

[Xen patchbot -unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>]

# HG changeset patch
# User emellor@xxxxxxxxxxxxxxxxxxxxxx
# Node ID 12c3b4463cba7e1d9949f93d615b8a5584481311
# Parent  b47b795857727e0489812cdaf7881f0c94bf0d70
Added description of the behaviour of rename-restart.

Signed-off-by: Ewan Mellor <ewan@xxxxxxxxxxxxx>

diff -r b47b79585772 -r 12c3b4463cba docs/man/xmdomain.cfg.pod.5
--- a/docs/man/xmdomain.cfg.pod.5       Mon Nov  7 11:36:53 2005
+++ b/docs/man/xmdomain.cfg.pod.5       Mon Nov  7 14:06:00 2005
@@ -120,8 +120,10 @@
 =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?)
+domain can be restarted in it's place.  The old domain will be renamed with
+a suffix -1, -2, etc, and assigned a new random UUID; the new domain will
+keep the original name and UUID.  The old domain will release the devices that
+it holds, so that the new one may take them.
 
 =back
 

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