From 2c7a4f62dc6e21ebd25b64c09f249e7773cf1f59 Mon Sep 17 00:00:00 2001 From: Keir Fraser Date: Fri, 18 Jan 2008 13:43:26 +0000 Subject: Clarify 'xm mem-set' and 'xm vcpu-set' requirements in documentation. From: Richard W.M. Jones Signed-off-by: Keir Fraser --- docs/man/xm.pod.1 | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/man/xm.pod.1 b/docs/man/xm.pod.1 index 0195736e26..74b58dbf14 100644 --- a/docs/man/xm.pod.1 +++ b/docs/man/xm.pod.1 @@ -254,9 +254,12 @@ domain, as it may balloon down its memory to give more back to the OS. =item B I I -Set the domain's used memory using the balloon driver. Because this -operation requires cooperation from the domain operating system, there -is no guarantee that it will succeed. +Set the domain's used memory using the balloon driver. + +Because this operation requires cooperation from the domain operating +system, there is no guarantee that it will succeed. This command will +definitely not work unless the domain has the required paravirt +driver. B There is no good way to know in advance how small of a mem-set will make a domain unstable and cause it to crash. Be very @@ -392,6 +395,10 @@ Attempting to set the VCPUs to a number larger than the initially configured VCPU count is an error. Trying to set VCPUs to < 1 will be quietly ignored. +Because this operation requires cooperation from the domain operating +system, there is no guarantee that it will succeed. This command will +not work with a full virt domain. + =item B [I] Lists VCPU information for a specific domain. If no domain is -- cgit v1.2.3