External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-07-16 22:57:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

Clarify virsh documentation.

Browse Source 
* docs/virsh.pod: Clarify virsh documentation on when you can
          set memory and vCPUs.
This commit is contained in:
Richard W.M. Jones 2008-01-25 12:03:05 +00:00
parent aab826d4cc
commit b17caa80d1
2 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ChangeLog
View File

@ -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

6
docs/virsh.pod
View File

@ -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