ia64/xen-unstable
changeset 7654:12c3b4463cba
Added description of the behaviour of rename-restart.
Signed-off-by: Ewan Mellor <ewan@xensource.com>
Signed-off-by: Ewan Mellor <ewan@xensource.com>
author | emellor@leeni.uk.xensource.com |
---|---|
date | Mon Nov 07 15:06:00 2005 +0100 (2005-11-07) |
parents | b47b79585772 |
children | a05e55c919c1 |
files | docs/man/xmdomain.cfg.pod.5 |
line diff
1.1 --- a/docs/man/xmdomain.cfg.pod.5 Mon Nov 07 12:36:53 2005 +0100 1.2 +++ b/docs/man/xmdomain.cfg.pod.5 Mon Nov 07 15:06:00 2005 +0100 1.3 @@ -120,8 +120,10 @@ real issue. 1.4 =item I<rename-restart> 1.5 1.6 The old domain will not be cleaned up, but will be renamed so a new 1.7 -domain can be restarted in it's place. (TODO: what does this mean for 1.8 -resources? What is the renamed name?) 1.9 +domain can be restarted in it's place. The old domain will be renamed with 1.10 +a suffix -1, -2, etc, and assigned a new random UUID; the new domain will 1.11 +keep the original name and UUID. The old domain will release the devices that 1.12 +it holds, so that the new one may take them. 1.13 1.14 =back 1.15