Clarify virsh documentation.

        * docs/virsh.pod: Clarify virsh documentation on when you can
          set memory and vCPUs.

diff --git a/ChangeLog b/ChangeLog
index 516adc4c8784cb6bbce8d8a831ca628ab01987d6..5493e517f35ecb9dddfe80d798625cf5fb6b2bcf 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+Fri Jan 25 12:00:00 BST 2008 Richard W.M. Jones <rjones@redhat.com>
+
+       Clarify virsh documentation.
+       * docs/virsh.pod: Clarify virsh documentation on when you can
+         set memory and vCPUs.
+
 Fri Jan 25 10:46:32 CET 2008 Daniel Veillard <veillard@redhat.com>
 
        * src/xen_internal.c: fix an erronous use of VIR_DOMAIN_NONE instead

diff --git a/docs/virsh.pod b/docs/virsh.pod
index 62e05f35faed359ea5d689664e59ba424d99434d..8166db73dfb333fc37806e33121df4559be0771f 100644 (file)
--- a/docs/virsh.pod
+++ b/docs/virsh.pod
@@ -290,6 +290,9 @@ Change the current memory allocation in the guest domain. This should take
 effect immediately. The memory limit is specified in
 kilobytes.
 
+For Xen, you can only adjust the memory of a running domain if the
+domain is paravirtualized or running the PV balloon driver.
+
 =item B<setmaxmem> I<domain-id> B<kilobytes>
 
 Change the maximum memory allocation limit in the guest domain. This should
@@ -302,6 +305,9 @@ Change the number of virtual CPUs active in the guest domain. Note that
 I<count> may be limited by host, hypervisor or limit coming from the 
 original description of domain.
 
+For Xen, you can only adjust the virtual CPUs of a running domain if
+the domain is paravirtualized.
+
 =item B<shutdown> I<domain-id>
 
 Gracefully shuts down a domain.  This coordinates with the domain OS