Hi Scott,

We've just finished updating the man pages for setvcpus, setmem, and setmaxmem.

This now needs the info for these commands updated in the RHEL 6.1 VG.  Probably this part here:

  http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization/chap-Virtualization-Managing_guests_with_virsh.html


For reference, this is the info in the updated man pages (not sure if you'd want
to copy it wholesale, or just parts of it, or what):

  setvcpus domain-id count optional --maximum --config --live

    Change the number of virtual CPUs active in a guest domain.  By
    default, this command works on active guest domains.  To change the
    settings for an inactive guest domain, use the --config flag.

    The count value may be limited by host, hypervisor, or a limit coming
    from the original description of the guest domain.  For Xen, you can only
    adjust the virtual CPUs of a running domain if the domain is
    paravirtualized.

    If the --config flag is specified, the change is made to the stored XML
    configuration for the guest domain, and will only take effect when the
    guest domain is next started.

    If --live is specified, the guest domain must be active, and the change
    takes place immediately.  Both the --config and --live flags may be
    specified together if supported by the hypervisor.

    When neither the --config nor --live flags are given, the --live flag is
    assumed and the guest domain must be active.  In this situation it is up
    to the hypervisor whether the --config flag is also assumed, and
    therefore whether the XML configuration is adjusted to make the change
    persistent.

    The --maximum flag controls the maximum number of virtual cpus that
    can be hot-plugged the next time the domain is booted.  As such, it must
    only be used with the --config flag, and not with the --live flag.


  setmem domain-id kilobytes

    Immediately change the current memory allocation for an active guest
    domain.

    Some hypervisors require a larger granularity than kilobytes, and requests
    that are not an even multiple will either be rounded down or rejected.  For
    example, vSphere/ESX rejects the parameter unless the kB argument is
    evenly divisible by 1024 (that is, the kB argument happens to represent
    megabytes).

    For Xen, you can only adjust the memory of a running domain if the domain
    is paravirtualized or running the PV balloon driver.

    Note, this command only works on active guest domains.  To change the
    memory allocation for an inactive guest domain, use the virsh edit command
    to update the XML <currentMemory> element.


  setmaxmem domain-id kilobytes

    Change the maximum memory allocation limit for an inactive guest domain.

    This command works for at least the Xen and vSphere/ESX hypervisors, but
    not for QEMU/KVM.

    Some hypervisors require a larger granularity than kilobytes, rounding down
    or rejecting requests that are not an even multiple of the desired amount.
    vSphere/ESX is one of these, requiring the parameter to be evenly divisible
    by 4MB.  For vSphere/ESX, 263168 (257MB) would be rejected because it's
    not a multiple of 4MB, while 266240 (260MB) is valid.

    Note, to change the maximum memory allocation for a QEMU/KVM guest
    domain, use the virsh edit command instead to update its XML <memory>
    element.

Verify that table 30.2 refers the user to the man page for more details.

Red_Hat_Enterprise_Linux-Virtualization-6-web-en-US-3.2-051.el5