14 Jan
2011
14 Jan
'11
4:25 p.m.
On 15/01/2011, at 2:14 AM, Justin Clift wrote:
Hi Matthias,
Do you know if the virsh "setmaxmem" has the same MB granularity as "setmem" (on vSphere/ESX)?
Ignore this. Found the info in the header in our src/vmx/vmx.c file: def->mem.max_balloon = <value kilobyte> <=> memsize = "<value megabyte>" # must be a multiple of 4, defaults to 32 def->mem.cur_balloon = <value kilobyte> <=> sched.mem.max = "<value megabyte>" # defaults to "unlimited" -> def->mem.cur_balloon = def->mem.max_balloon def->mem.min_guarantee = <value kilobyte> <=> sched.mem.minsize = "<value megabyte>" # defaults to 0 Looks like MB granularity as well. :) + Justin