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.

diff --git a/src/libxl/libxl_driver.c b/src/libxl/libxl_driver.c
index 8087c27797957f0d1cfe336425f4d72129f4bdbd..019f04f7713f21296333de680598717d247a94e1 100644 (file)
--- a/src/libxl/libxl_driver.c
+++ b/src/libxl/libxl_driver.c
@@ -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;
 

diff --git a/src/vz/vz_driver.c b/src/vz/vz_driver.c
index 8fa79578e3651453fb2605f314d9b1f4a2f1013f..2eb025c5ebe89d971e0cc7d714e252fcb7904d01 100644 (file)
--- a/src/vz/vz_driver.c
+++ b/src/vz/vz_driver.c
@@ -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;
 }