On 14/01/2011, at 5:30 AM, Eric Blake wrote:
> Not quite. The virsh command always takes kB, but vSphere rejects the
> parameter unless the kB argument is evenly divisible by 1024 (that is,
> the kB argument happens to represent megabytes).
>
> Maybe more like:
>
> Some hypervisors require a larger granularity than kilobytes, and
> requests that are not an even multiple will either be rounded down or
> rejected.
Heh, nice text. Combining both of your above sounds even better though I
reckon:
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 <memory> element.
Workable?
--
libvir-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/libvir-list
