libxl: vz: Use accessor instead of direct access for max_balloon

Commits 45697fe5 and f863ac80 used direct access to the variable instead
of the preferred accessor method.
This commit is contained in:
Peter Krempa 2015-09-16 14:00:02 +02:00
parent e2863e7768
commit 5dd61a168f
2 changed files with 2 additions and 2 deletions

View File

@ -553,7 +553,7 @@ libxlAddDom0(libxlDriverPrivatePtr driver)
vm->def->vcpus = d_info.vcpu_online;
vm->def->maxvcpus = d_info.vcpu_max_id + 1;
vm->def->mem.cur_balloon = d_info.current_memkb;
vm->def->mem.max_balloon = d_info.max_memkb;
virDomainDefSetMemoryInitial(vm->def, d_info.max_memkb);
ret = 0;

View File

@ -1200,7 +1200,7 @@ vzDomainGetMaxMemory(virDomainPtr domain)
if (!(dom = vzDomObjFromDomain(domain)))
return -1;
ret = dom->def->mem.max_balloon;
ret = virDomainDefGetMemoryActual(dom->def);
virObjectUnlock(dom);
return ret;
}