This adds a small section to the documentation for these virsh commands to clarify that you can't use them on running, fullvirt domains under Xen.

Rich.

--
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom.  Registered in
England and Wales under Company Registration No. 03798903
Index: docs/virsh.pod
===================================================================
RCS file: /data/cvs/libvirt/docs/virsh.pod,v
retrieving revision 1.8
diff -u -r1.8 virsh.pod
--- docs/virsh.pod	28 Sep 2007 14:28:13 -0000	1.8
+++ docs/virsh.pod	17 Jan 2008 17:37:33 -0000
@@ -290,6 +290,9 @@
 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 @@
 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

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Reply via email to